On Tue, 04 Feb 2014 14:32:52 -0200, Lance Java <lance.j...@googlemail.com>
wrote:
I have a sneaking suspicion that trying to implement this you would end
up writing a custom implementation of <script> and eval(...) to achieve
tapestry's current behaviour
Nope, I was thinking of encoding the JavaScript code in the URL, probably
in Base64, and write a Dispatcher that would catch these requests, extract
the code from the URL and return it. Or store the code in memory, put a
token in the URL and use the token to retrieve the stored code.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
