W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > September to December 1995

Re: Byteranges with 206 partial content

From: Alexei Kosut <akosut@nueva.pvt.k12.ca.us>
Date: Mon, 13 Nov 1995 17:13:45 -0800 (PST)
To: Ari Luotonen <luotonen@netscape.com>
Cc: http-wg mailing list <http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com>
Message-Id: <Pine.HPP.3.91.951113170938.14233A-100000@ace.nueva.pvt.k12.ca.us>
On Mon, 13 Nov 1995, Ari Luotonen wrote:

> An additional feature is to say "give me a range if the document
> hasn't changed, but if it has, send me the entire document".  Similar
> to If-modified-since, but still quite different...  What would you
> call such a header?

You wouldn't want to use If-modified-since itself, since that would cause
incorrect behavior with non-byte range compatible servers. Me, I would
incorporate it into the range request header, since it's part of that
function. Something like: 

Request-Range: Sun, 06 Nov 1994 08:49:37 GMT; bytes=0-499

That would seem to make sense to me, since you're saying "send me the 
first 500 bytes of the document if it hasn't been modified since this 
date, otherwise send it all."Of course, you'd still want to be able to 
say

Request-Range: bytes=0-499

For those cases where you really just want a certain byte range from a
document, even if it's changed (or if you've never seen it before). I'd
assume servers are smart enough to tell the difference. 

> I will re-vamp a new version of the byterange draft reflecting these
> changes, and will submit it for review in http-wg shortly.

Great!

--/ Alexei Kosut <akosut@nueva.pvt.k12.ca.us> /--------/ Lefler on IRC
----------------------------/ <http://www.nueva.pvt.k12.ca.us/~akosut/>
The viewpoints expressed above are entirely false, and in no way
represent Alexei Kosut nor any other person or entity. /--------------
Received on Monday, 13 November 1995 17:22:38 EST

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:31:35 EDT