UrlEncodedQueryString CCC request

[Michael McMahon]

We have been asked by the CCC to go back and reconsider the design of 
the proposed
UrlEncodedQueryString class/API and to consider aligning it with the 
URIBuilder class
that has been proposed in JSR311. Also, the particular concern expressed 
by the CCC
is that we possibly restricted the scope of the class too much.

What I think we would like to achieve (for Java SE) is a general purpose 
URI builder that is not
specifically tied to any particular type of web application.

When Richard initially proposed the UrlEncodedQueryString, it was more 
like a URIBuilder
but our concern (which I think is still valid) is that a Java SE class 
for constructing URIs
must be solely based on defined standards (the URI rfcs), rather than on 
ad-hoc (albeit commonly used)
conventions in the world of web applications. Specifically, I don't 
think we can impose
any additional structure on URIs that is not explicitly specified in the 
relevant URIs.
But if other people have a different view on this, I'm interested to 
discuss it.

A reference for the JSR311 class is at
https://jsr311.dev.java.net/nonav/javadoc/index.html

and Paul Sandoz's blog entry talking about it is at
http://blogs.sun.com/sandoz/entry/building_uris

The javadoc for the proposed UrlEncodedQueryString is attached in a zip file

Thanks,
Michael.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: docs.zip
Type: application/octet-stream
Size: 25965 bytes
Desc: not available
Url : http://mail.openjdk.java.net/pipermail/net-dev/attachments/20071011/8f215521/docs.zip