- From: Yves Lafon <ylafon@w3.org>
- Date: Wed, 9 Sep 2009 08:42:33 -0400 (EDT)
- To: Raphaël Troncy <Raphael.Troncy@cwi.nl>
- cc: public-media-fragment@w3.org
On Wed, 9 Sep 2009, Raphaël Troncy wrote:
> With this option, one could then express a Range request, for example, for a
> time interval where the start time would be expressed in npt and the end time
> in smpte-30. Is this what you call 'flexibility'? I'm afraid that it also
> adds extra-complexity which is not really required. As you say, this solution
> has also the drawback of we cannot use Accept-Ranges.
Yes flexible, but dangerous ;) But it's a way to cope with the duration
issue in the smpte case (if it exists)
> Question: is it possible to have multiple values for the Accept-Ranges
> header? I can see that:
> Accept-Ranges: none
> Accept-Ranges: bytes
> are valid!
It's none or a comma separated list of units.
And two headers like that may fold in one using a comma separated list.
--
Baroula que barouleras, au tiéu toujou t'entourneras.
~~Yves
Received on Wednesday, 9 September 2009 12:42:41 UTC