Hi,
as far as I know, Tapestry's URLEncoder allows you to not think about
encoding, it forces to UTF-8.
Default URLEncoder asks you to specify encoding as a separate parameter,
which you normally pass as another URL parameters, for example, look at
ie/oe parameters that Safari adds to Google requ
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
I don't see why you need to make the var dynamic, as it contains a mutable
value (a promise) itself.
However, this does bring to mind an idea for 5.5, that Tapestry could
define a dynamic Var to contain the registry, and bind that Var whenever it
invokes a Clojure function via the interop.
On Mon
