Richard Kennard wrote:
Michael,
I just thought I'd tackle this point in detail...
Here we agree! And with the current version of the code, this works...
URLEncodedQueryString queryString =
URLEncodedQueryString.create();
queryString.setParameter( "a", "x&y" );
queryString.setParameter( "b", "u;v" );
assertTrue( "a=x%26y&b=u%3Bv".equals(
queryString.toString() ));
queryString = URLEncodedQueryString.parse(
queryString.toString() );
assertTrue( "x&y".equals( queryString.getParameter( "a" )));
assertTrue( "u;v".equals( queryString.getParameter( "b" )));
...is that what you were suggesting?
That's fine then. So long as the whole thing is fully consistent, I'm ok
with it.
All that's needed is an additional parse() method which specifies the
separator char.
Again, the HTML spec doesn't say 'when one character is the separator
char then the others are normal characters', so I don't see how you
can specify a single separator char?
If we can get this cleared up I'll post the new version of the class
(renamed to use Url instead of URL).
Good. Still haven't heard back from the CCC, but I will update the
request with your next API
version anyway.
Thanks
Michael
