[Fwd: Re: URLEncodedQueryString]

2007-07-16 Thread Michael McMahon
--- Begin Message --- 1. How about setParameters(String name, List values) so that I can set a multivalued parameter in one call? 2. Why undefined result when input string is not a url-encoded query string? Why not throw an Exception? 3. public static UrlEncodedQueryString create (Map> p

[Fwd: Re: URLEncodedQueryString]

2007-07-16 Thread Michael McMahon
--- Begin Message --- Questions (Sorry, of this has come up before): 1) Why have overloaded versions of toString and parse. Why not one method called setSeparator? 2) Does getParameterNames return multiple entries for multiple name value pairs. I think not. 3) Do we really need removeParamete

[Fwd: Re: URLEncodedQueryString]

2007-07-16 Thread Michael McMahon
--- Begin Message --- Forget question 4. I can see that Number.toString will handle this. -Chris. Christopher Hegarty - Sun Microsystems Ireland wrote: Questions (Sorry, of this has come up before): 1) Why have overloaded versions of toString and parse. Why not one method called setSeparator

[Fwd: Re: URLEncodedQueryString]

2007-07-16 Thread Michael McMahon
--- Begin Message --- Max (Weijun) Wang wrote: 1. How about setParameters(String name, List values) so that I can set a multivalued parameter in one call? I think the most likely use case, is when you dynamically add the parameters one at a time, but that case is certainly possible. But I'd

Re: URLEncodedQueryString

2007-07-16 Thread Michael McMahon
Christopher Hegarty - Sun Microsystems Ireland wrote: Questions (Sorry, of this has come up before): 1) Why have overloaded versions of toString and parse. Why not one method called setSeparator? We need to support both separator types in the same input strings. Though I thought that the orig