Hi, One of the things I do in my day job is helping people develop and debug HTTP-based APIs and services.
Often, because services are composed across several layers of caching, aggregation, etc. and pull in things like databases and other services, people want to get a "trace" view that shows the whole picture, rather than just one component. One of the ways to do this is to put the information into HTTP response headers, so that downstream clients can consume it. Making this sort of information visible in Firebug would be awesome. E.g., if a server can supply information about how it's spent it's time, the waterfall can give much more detailed information than just 'waiting'. Upstream caches could expose more information to show whether it was a hit, a miss, and so on. Some caches (e.g., Squid and Traffic Server) already make this information available in proprietary format. Back-end servers how the response was generated, and with a bit more work, can help map out where the components of a response were drawn from, with the overhead of each made visible. Would folks at Firebug be interested in working on this? It would mean defining a few new response headers that describe the trace information, along with the appropriate UI changes. It would probably also require supporting HTTP trailers for those headers, since this sort of information is often not available until after the response is generated. Cheers, -- 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.
