I see a potential problem with using '?' because it is already used
for forms. What happens if someone has a form with a field named
"byterange"? We are better off having the name space for form fields
separate from that of URL parameters.
> Please. Let's not expand on this. It forces servers to have a much more
> intimate knowledge of the content they serve than is necessary. Let's
> define how byte ranges work and leave the nasty WWW object model for
> another day and another syntax.
I generally agree with this, though I might not have put it so strongly.
On the other hand it is fine for servers to implement server specific
parameters with special meaning for that server. There are a number of
such in the server that I wrote. If, as in the case of byterange, it
turns out that several implementors want the same functionality it makes
sense to try to standardize.