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

Re: Multiple ranges in the same HTTP request.

From: Conrad Parker <conrad@metadecks.org>
Date: Sat, 24 Apr 2010 00:09:31 +0900
Message-ID: <q2jdba6c0831004230809tcfb07dc8x437ea2cd83b6b63b@mail.gmail.com>
To: RaphaŽl Troncy <raphael.troncy@eurecom.fr>
Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Jakub.Sendor@eurecom.fr, public-media-fragment@w3.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 ...

Received on Friday, 23 April 2010 15:10:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:52:44 UTC