- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Wed, 17 Mar 2010 07:58:14 +1100
- To: Yves Lafon <ylafon@w3.org>
- Cc: raphael.troncy@eurecom.fr, Media Fragment <public-media-fragment@w3.org>
On Wed, Mar 17, 2010 at 3:23 AM, Yves Lafon <ylafon@w3.org> wrote: > On Tue, 9 Mar 2010, Raphaël Troncy wrote: > >> # A new header named 'Content-Range-Mapping' will be introduced, which >> purpose is to expressed a mapping of a Content Range between 2 units (e.g. >> bytes and seconds) > > Range processing can't introduce new entity headers Can you explain why? There is no existing infrastructure for any range handling other than bytes, so if our range handling requires an additional, informative header, why sholdn't it be possible to introduce it? Regards, Silvia.
Received on Tuesday, 16 March 2010 20:59:06 UTC