W3C home > Mailing lists > Public > www-talk@w3.org > May to June 1995

Re: Byte ranges -- formal spec proposal

From: Carl von Loesch <Carl.von.Loesch@arbi.informatik.uni-oldenburg.de>
Date: Sun, 21 May 1995 23:24:39 +0200 (MET DST)
Message-Id: <m0sDIUK-000AgFC@tuerkis.Informatik.Uni-Oldenburg.DE>
To: masinter@parc.xerox.com
Cc: www-talk@www10.w3.org
| > It has been suggested that byte ranges could be supported by either a new
| > HTTP method or by a new HTTP header.  The point of byteranges is to allow
| > HTML anchors to request a range of bytes from a document.

But I prefer the URL method much more, as it makes perfectly sense to
request a part of a binary from an FTP server, or just the signature of
a news posting, or a range in a gopher text file.

I like common syntax ("methods" in OOP).. even if the semantics differ
slightly.. whatever seems applicable sounds like a good choice to me.
I wouldn't want it in the headers.

Larry Masinter typeth:
| Except for the case of extracting individual segments out of larger
| ascii files, though, I'm having trouble thinking of any real examples
| of this, and, in particular, any examples where the documents aren't
| text/plain.

Ever tried to download netscape from overseas?

And no, I don't want to explain every netscape user how to download using
ftp and REGET, as it would circumvent any hope of having the stuff cached
by the WWW proxies.

Explain every user how to ftp from mirrors?
We're working on that, but the number of net newbies is growing too fast.

P.S.  Don't forget s/byterange/bytes/	;)

     _______					  http://home.pages.de/~lynx/
irc: SymLynX		Carl v. Loesch			  lynx@net.pages.de

Received on Sunday, 21 May 1995 17:29:56 UTC

This archive was generated by hypermail 2.4.0 : Monday, 20 January 2020 16:08:17 UTC