- From: <bugzilla@jessica.w3.org>
- Date: Tue, 04 Oct 2011 05:19:32 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14310 --- Comment #5 from Offbeatmammal <offbeatmammal@gmail.com> 2011-10-04 05:19:31 UTC --- some detail on the Akamai use-case at http://webspherehelp.blogspot.com/2009/07/understanding-akamai-headers-to-debug.html though I suspect it would be difficult to produce a definitive list which remains complete so maybe a suggestion would be to list the headers we want to listen to for a specific request (which would tie in with setting the specific pragma headers to get Akamai to share the information to the client) Similar to http://www.w3.org/Bugs/Public/show_bug.cgi?id=14186 this will help to provide more detailed debugging info - especially useful when dealing with video/audio I love the idea of exposing the information (especially around response times) to the Web Timings - especially as we start to venture into the world of adaptive streams (fMPEG, DASH, HLS, Smooth Streaming or where-ever things net out) where being able to see response times, source, response codes etc for each chunk becomes important to get a good idea of the end user quality experience (beyond the simple "did it load or not" knowing if it buffered, how much it buffered, who it buffered for (and where) etc becomes very useful -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 4 October 2011 05:19:34 UTC