- From: Raphaël Troncy <raphael.troncy@eurecom.fr>
- Date: Wed, 17 Nov 2010 10:50:38 +0100
- To: Philip Jägenstedt <philipj@opera.com>
- CC: public-media-fragment@w3.org
> For example, we can't > send additional HTTP headers based on the presence of #t=1 on the first > request, unless put into the URL/URI/IRI spec itself, which I doubt will > happen. Why not? This is exactly what we have discussed at the F2F meeting, read http://www.w3.org/2010/11/02-mediafrag-minutes.html#item05. This has lead to "ACTION-197: Raphaël to also add in the intro of Section 5 a paragraph explaining the optimistic processing of fragments (using ranges in seconds)". This is a proposal, but I think worth to investigate. > Again, the issue Silvia brought up was specifically if we could use MF > on web pages, i.e. with HTML. http://example.com/video.webm#t=1 should > just work, whether in <video src> or in the address bar. Assume that the optimistic processing of fragments is implemented by browsers, just for the time dimension (95% of the use cases) using range requests expressed in seconds, then, before knowing what the resource would be, the browser has issued a range request: - if this is a video, then, great it works. - if this is a html page, scroll to the section id - if this is a html page embedding a video (e.g. a Youtube page), and that there is no section id "t=...", then play the video from t Just a silly proposal. Raphaël -- Raphaël Troncy EURECOM, Multimedia Communications Department 2229, route des Crêtes, 06560 Sophia Antipolis, France. e-mail: raphael.troncy@eurecom.fr & raphael.troncy@gmail.com Tel: +33 (0)4 - 9300 8242 Fax: +33 (0)4 - 9000 8200 Web: http://www.eurecom.fr/~troncy/
Received on Wednesday, 17 November 2010 09:53:45 UTC