Hi guys, I'm just wondering why Tapestry decided to build their own URLEncoder over using an existing one like java.net.URLEncoder? I'd like to clean up my URLs removing a lot of the encoding making them more search friendly, so I'm wondering what the impact of overriding the URLEncoder service and implementing a more standard one would be? Thanks.
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
