W3C home > Mailing lists > Public > public-media-fragment@w3.org > April 2010

Re: Multiple ranges in the same HTTP request.

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Sat, 24 Apr 2010 18:37:04 +1000
Message-ID: <p2v2c0e02831004240137ra59f24w69bf2017053c3955@mail.gmail.com>
To: Conrad Parker <conrad@metadecks.org>
Cc: RaphaŽl Troncy <raphael.troncy@eurecom.fr>, Jakub.Sendor@eurecom.fr, public-media-fragment@w3.org
2010/4/24 Conrad Parker <conrad@metadecks.org>:
> 2010/4/24 RaphaŽl Troncy <raphael.troncy@eurecom.fr>:
>>> There is indeed no specification of this yet and a ABNF is still in
>>> the pipeline for this.
>>> I guess if we are conforming with other HTTP headers where there were
>>> multiple values for one header, it would be:
>>>
>>> Range: track=audio, t:npt=10-20
>>> It would return seconds 10-20 of the track called "audio" in the resource.
>>
>> +1 for this! Awaiting for the ABNF of the headers to set this in marble.
>> Yves, ACTION-123 [1]?
>
> How is "track=audio" a Range? it seems semantically much more like a
> way of filtering the content (making a view). There's nothing
> contiguously range-y about it ...


It can be mapped to byte ranges - that's what "range" means. I believe
Davy has an implementation of this working already.

But of course the server can always reply with an error that it cannot
resolve the range if it doesn't support track as a range dimension.

Cheers,
Silvia.
Received on Saturday, 24 April 2010 08:37:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 September 2011 12:13:38 GMT