- From: <bugzilla@jessica.w3.org>
- Date: Wed, 05 Oct 2011 00:57:04 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14310 --- Comment #6 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> 2011-10-05 00:57:02 UTC --- I had similar feedback from YouTube: "Identifying the server is an essential part in diagnosing streaming issues. Load balancing happens at DNS resolving level, which is not visible to JS. The hostname in the URL could resolve to any of the hundreds of server IPs distributed around the globe. The server might also use HTTP 302 response to redirect a request to another server, and redirects are not visible to JS either. It would help a lot if browsers can export the IP address of the server. If the IP address is not exposed to JS, another way to identify a server is to insert the server id into the video file header and having the client read video header. Does the HTML5 video tag expose an interface for accessing metadata in the video headers?" I had this discussion as part of the video metrics discussion, see http://wiki.whatwg.org/wiki/Video_Metrics and http://www.w3.org/Bugs/Public/show_bug.cgi?id=12399 . -- 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 Wednesday, 5 October 2011 00:57:06 UTC