- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Mon, 13 Apr 2009 16:03:14 +1000
- To: Yves Lafon <ylafon@w3.org>
- Cc: Conrad Parker <conrad@metadecks.org>, Media Fragment <public-media-fragment@w3.org>
On Mon, Apr 13, 2009 at 4:55 AM, Yves Lafon <ylafon@w3.org> wrote: > On Mon, 13 Apr 2009, Conrad Parker wrote: > >> 2009/4/13 Yves Lafon <ylafon@w3.org>: >>> >>> On Sun, 12 Apr 2009, Silvia Pfeiffer wrote: >>> >>>> Example: >>>> >>>> GET http://example.com/fragf2f.mp4 HTTP/1.1 >>>> Accept: video/* >>>> Range: seconds=12-21 >>>> X-Accept-Range-Redirect: bytes >>> >>> One thing that I wonder is what happen if the reply is with two Range: >>> header, one in bytes, one in seconds. >> >> What is the use-case for both HTTP request headers? > > Do the mapping between seconds and bytes. Then I think the User Agent should be encouraged (or even required) to only send the byte ranges, since they can be resolved without a further mapping effort on the server side. Cheers, Silvia.
Received on Monday, 13 April 2009 06:04:09 UTC