Current time: 11-01-2020, 12:39 PM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
different traffic shaping behaviour between version 2.15 and 2.18 agent
03-08-2016, 12:16 AM
Post: #8
RE: different traffic shaping behaviour between version 2.15 and 2.18 agent
I don't think it's a difference in the actual traffic shaping (the dns and socket connect times look roughly equivalent) but rather changes in processing the dev tools request data from Chrome that improved the accuracy (and particularly bytes) reporting in 2.19.

That said, if you grab the latest agent from the public server (or trunk), I finally got code working that accesses the decrypted byte streams directly for Chrome so the timings no longer require decoding and trusting dev tools and it can report the timings directly from the network like it does for HTTP (non-S) and for all of the other browsers.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: different traffic shaping behaviour between version 2.15 and 2.18 agent - pmeenan - 03-08-2016 12:16 AM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)