Re: Comments on Byte range draft

• From: Gavin Nicol <gtn@ebt.com>
• Date: Sun, 12 Nov 1995 07:51:05 -0500
• To: montulli@mozilla.com
• Cc: fielding@avron.ICS.UCI.EDU, masinter@parc.xerox.com, ari@netscape.com, john@math.nwu.edu, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
• Message-Id: <199511121251.HAA04403@ebt-inc.ebt.com>

>You and Larry are looking at this problem with blinders on.
>There are many more uses for byterange URL's than simply
>PDF files.  For instance Netscape 2.0 uses byteranges to
>request parts of files that it didn't get the last time
>you came to a page. 

And then you have to reparse the entire document again, and re-render
it, possibly ignoring the errors caused by the file being
incomplete. This is great for small pages, but if you try fetching
small peices of a 5MB document, it makes no sense. 

Byte ranges are a lazy replacement for a general naming mechanism.

Received on Sunday, 12 November 1995 04:49:30 UTC