Re: Byte ranges -- formal spec proposal

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Ari Luotonen: "FYI: Summary #1 of byte ranges"
• Previous message: Gavin Nicol: "Re: Byte ranges -- formal spec proposal"
• Maybe in reply to: Ari Luotonen: "Byte ranges -- formal spec proposal"

Gavin Nicol <gtn@ebt.com> writes:
> It is most unlikely that anyone, or anything, could specify an
> arbitrary byte range from an HTML document, and end up with
> something legal (ie. displayable by itself).

It gets even worse when you consider non-ASCII character encodings.  
 Given just a chunk of bytes, you might not even be able to figure  
out what characters those bytes map to.  And what about servers  
which can vend the same document in multiple character encodings?   
If I have a document stored in UTF-8 and can vend it in ShiftJIS or  
EUC depending on the Accept-Charset: parameter, it seems that  
"byterange" as part of a URL for this document is not well defined.

Linus Upson

• Next message: Ari Luotonen: "FYI: Summary #1 of byte ranges"
• Previous message: Gavin Nicol: "Re: Byte ranges -- formal spec proposal"
• Maybe in reply to: Ari Luotonen: "Byte ranges -- formal spec proposal"