- From: Yves Lafon <ylafon@w3.org>
- Date: Mon, 1 Sep 2008 11:01:47 -0400 (EDT)
- To: Jamie Lokier <jamie@shareable.org>
- cc: Kris Zyp <kris@sitepen.com>, Julian Reschke <julian.reschke@gmx.de>, ietf-http-wg@w3.org
On Mon, 1 Sep 2008, Jamie Lokier wrote:
> Right now, cache range operations are independent of content type.
Well, just because 'bytes' a pretty much independant of CT :)
> (Btw, one can easily imagine ranges "characters", "xpath", "xquery",
> "grep"... even "session". I'm not sure if that's a desirable road to
> go down. Maybe it would be very useful.)
I read ranges as "a part, possibly the whole part (0-) of a document"
in the case of characters for text-based documents, it's ok, but grep,
xpath won't be able to access the whole document using the "0-" syntax.
But maybe even the way ranges are defined may change (after all it's
defined as "byte-range-resp-spec" now), still I find this perverting the
meaning of ranges and go in the transformation domain.
--
Baroula que barouleras, au tiéu toujou t'entourneras.
~~Yves
Received on Monday, 1 September 2008 15:02:21 UTC