Two examples of common serial events that depend on server data are:
- Redirect to a new page as soon as feedback to a server is done.
- Ping a server once an answer from a different server was received.
How can you examine and validate that the events are indeed not only firing in serial order, but are happening ASAP, i.e. no accidental waiting between events is taking place?
Fiddler’s “timeline” tab can help soothe away your worries!
- Using CTRL+CLICK, select the two (or more) events you wish to inspect:
- Open the “timeline” tab and look at the graph:
If you’ll notice that the horizontal axis for this graph represents time, you’ll be able to see that the event sending data to the “redirect” URL started as soon as an answer from “report.json” was returned from the server. Joy!
Finally, remember that you can select more than two events if needed, so more complex debugging scenarios can also be examined this way.
No comments:
Post a Comment