Re: Byte ranges -- formal spec proposal

>We're talking about potentially HUGE documents, which is the very
>reason why byteranges make sense with them.  So caching them, and
>possibly reconstructing them from pieces, is a big win, and not doing
>that would be really silly.

Please define a document in the sense used above. DynaWeb can deal
with very very large documents (hundreds of megabytes even), and does
not use byte ranges at all, but rather uses the structure of the data
to decide which bits to send.

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).