The XHR Spy (XHRs displayed in the Console panel) panel and Net panel use different ways to measure HTTP timing.
The main difference is that the Net panel is using timing info coming from Necko (the underlying Firefox networking stuff) while the XHR Spy is using JS Date().getTime() object. This means that XHR Spy measurement is done in the main UI thread and so, can be influenced by JS execution on this thread. I would have to have a simple test case to prove this theory. Honza On Jul 26, 2:41 am, Daniel Dormont <[email protected]> wrote: > Hi, I'm debugging an application in Firefox that uses BOSH, which is > basically an Ajax long-polling implementation of XMPP. At any rate, > the way the protocol works is there should be a series of XHR calls > where one starts as soon as the previous one finishes, and all should > take the same length of time, in my case one minute. > > In the case I'm trying to debug, there's a certain XHR that shows in > the Net panel as having taken 1 minute 0 seconds, and that same > request in the Console shows 1 minute 58 seconds. I'm fairly certain > it's the same request because the Date headers match exactly. I'd like > to understand what could cause this difference. I'm assuming it's > something to do with the post response handling, but what does it mean > exactly? Does it literally mean that the XHR callback took 58 seconds > to execute? > > Unfortunately this behavior is not reliably reproducible in any way > that I'm able to determine, so I'm hoping that Firebug can give me a > better clue as to the real cause. > > thanks, > Dan -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
