W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2008

Re: issue 85 - range unit extensions

From: Jamie Lokier <jamie@shareable.org>
Date: Tue, 5 Aug 2008 19:30:08 +0100
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20080805183007.GB28513@shareable.org>

Julian Reschke wrote:
> 
> Mark Nottingham wrote:
> >...
> >Straw-man proposal (not exact text):
> >
> >Range-unit extensions SHOULD NOT be specific to any format. This is 
> >because caches are allowed to combine ranges from multiple responses, 
> >and to serve range requests out of cache; format-specific range units 
> >make it less likely that implementations will be able to do this 
> >(although there may be exceptions, hence the SHOULD NOT). An 
> >informational reference to p6 to highlight this to potential extenders 
> >would be a good idea.
> >...
> 
> Playing the devil's advocate: is there *any* range unit other than 
> "bytes" we can think of that is indeed independent of formats? Right 
> now, I can't think of any.

Since we're playing devil's advocate: to be independent of a subset of
formats, it's easy to imagine e.g. things which are specific to
everything under text/* or application/xml+*.

To be fully format independent, bytes have to be involved.  But there
are some interesting "ranges" such as "all portions of the entity
whose MD5 matches A,B,C,D,E,F,G or H", and other logical ways of
slicing and dicing bytes.  Some of those things are even logically
cachable and mergable.  Since we're playing devil's advocate :-)

-- Jamie
Received on Tuesday, 5 August 2008 18:30:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:54 GMT