- From: Raphaël Troncy <Raphael.Troncy@cwi.nl>
- Date: Sat, 22 Aug 2009 16:21:12 +0200
- To: Philip Jägenstedt <philipj@opera.com>
- CC: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Media Fragment <public-media-fragment@w3.org>
> In my opinion that is completely a UI design choice. My personal > preference is that ?query resources should be aligned to zero (ignoring > skeleton headers) and that #fragment resources should display the full > time-line with the ability to seek outside the specified range. > Different browsers will experiment with different solutions and if the > author isn't happy she/he could use a script-based interface more to > her/his liking. A big +1. >> An issue with any of our existing specs with fragments (#) that just >> occurred to me is: if the retrieval action only retrieves the >> specified segment, the browser has no way to figure out the length >> (start/duration) of the original resource. Maybe we need to introduce >> additional headers that would provide for that? > > That might help, but I don't really understand how this special > retrieval action is going to work yet. This issue has been solved during our last telecon. A response to a range request contains additionally the total length of the parent resource, so the UA will have "in hand" the bytes corresponding to the fragment it has requested _on_ the total duration of the parent resource, so the UA can display the full time-line, play only the fragment, and allow a user to seek outside. Cheers. 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.cwi.nl/~troncy/
Received on Saturday, 22 August 2009 14:22:19 UTC