> Here's my take. There is nothing wrong with j.u.URI as such. It just > needs a better parser that can deal with escaped and unescaped queries, > as well as be more lenient about common non-compliant behaviors, and > then construct the URI instance using a multi-arg constructor. It was > long on my virtual to-do list to open a feature request for pluggable > URI parsers in JIRA. Probably it is about time. > > Would that work for LimeWire? > > Oleg >
It almost certainly would work, however HttpClient would then be broken (as far as URI parsing goes) for everyone else. As others have pointed out (and as Tim explained to me in sad detail), URI is just basically broken when it comes to using it with the multi-arg constructors. It's flat-out impossible to recreate a URI with the multi-arg constructors and have it point to the correct resource. Sam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
