> If a new version of HTTP specifies the use of ';' rather than '&', the
> servlet engine could detect the HTTP version and decode appropriately.
What I don't understand is why it's a "problem" for HTTP at all, since it
seems to work just fine right now. I don't think it requires a new HTTP
version at all, and is already "wrong" according to the standard, but works.
I read about this being a bug already, and that if we wanted to use '&' in a
param, then we should have used the escaped #nn format. Yet, all the
browsers know how to handle this, so what's the fuss?!
> Specific to the servlet world, the HttpUtils.parseXXX methods would need
> to take an additional argument.
I was just curious, and it seems that because the '&' is only a convention,
it would have made sense to allow HttpUtils to allow for potentially
multiple separators ala strtok() and StringTokenizer, then it would have
been more flexible to meet the needs of the future, something a good API
always allows especially where there's a conflict with the current HTTP 4
spec.
David
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
