Re: Multiple ranges in the same HTTP request.

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 ...

Conrad.

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