The websocket messages does not have any kind of incoming timestamp.
It would be good to have that for multiple reasons (performance measurement, order of messages etc)
3 comments
Eric
Posted on:4 Feb 2017 06:00
It is what it is.
Bob
Posted on:4 Feb 2017 06:00
It should be 'timings' , not timers. Timers give wrong association.
Eric
Posted on:3 Feb 2017 06:00
Each WebSocketMessage has a Timers object; learn more here (https://www.fiddlerbook.com/om/html/689B8F41.htm) .
That said, there was a request to enable adding these as columns in the WebSocket Inspector for ease of reading; that seems like a fine idea.
Messages are presently ordered by ID; I believe that means that as the ID increases dtDoneRead will also be increasingly later.