So I think this is my last question in regards to this topic. If your doing your calculations on the fly, example converting aston marton to aston-martin which would mean you would later need to convert it back to aston marton to do the query, what do you do when the string naturally contains a dash. Example blue-purple, no spaces, but when decoded it would be decoded as blue purple with the assumption we replace dashes with space.
If I go the encoder route, I'd probably want something that handles all my parameter strings. It would be nice if tapestry offered you the ability to easily change it's encoder strategy. Example uses dashes instead of the zeros. -- View this message in context: http://tapestry.1045711.n5.nabble.com/How-to-remove-query-parmeter-from-url-string-tp5716922p5717004.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
