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

Re: Byte ranges -- formal spec proposal

From: Rainer Klute <klute@nads.de>
Date: Thu, 18 May 1995 08:36:06 +0200
Message-Id: <199505180636.IAA07823@heike.nads.de>
To: luotonen@netscape.com
Cc: Multiple recipients of list <www-talk@www10.w3.org>, klute@heike.nads.de
>                        BYTE RANGES WITH URLS AND HTTP
>   May 16, 1995

A very good proposal and it's nice to have it published and
discussed before it is implemented! This is the way Netscape Comm.
should always take.

Some minor points follow:

>Description of the byterange URL Parameter
>     * The byte range request is attached to the end of the URL,
>       separated by a semi-colon.

What is the "end of an URL"? In


where is the "end"? Is it before the question mark or behind
"blah". Would a byterange URL be



I'd prefer the former one because it integrates much more smothly
with existing applications.

>     * The first byte in file is byte number 1.

What is a file? There's not necessarily a file behind a URL, and to
the client this should be totally transparent. Let's call it
document or (even more general) entity.

As other responses indicate, it is more or less a matter of
taste whether to start with 0 or 1. Just pick one (not necessarily
1 :-)) and go for it.

>   If at some point there will be multiple simultaneous URL parameters,
>   they should be separated by the ampersand character (just like
>   multiple values are encoded in the FORM request).

Oh no, please don't pick the ampersand because of its SGMLish

BTW, some food for more thinking: It may be useful to invent some
notation for set operations, like

Best regards
Rainer Klute

  Dipl.-Inform. Rainer Klute        NADS - Advertising on nets
  Emil-Figge-Str. 80                Tel.: +49 231 9742570
D-44227 Dortmund                    Fax:  +49 231 9742571

Received on Thursday, 18 May 1995 02:37:35 UTC

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