solving reload

[Jamie Orchard-Hays <ja...@dang.com>]

I came across this article today comparing WEE and Rails and thought 
this would be food for thought here:

Imagine you look at a simple Wee application which displays an HTML 
anchor tag. If you click on that anchor, you’ll trigger an /action 
phase/, which eventually will find the registered callback associated 
with the anchor you have clicked on and invokes it. At the end of the 
/action phase/, Wee will forward you to a new (automatically generated) 
URL, which when requested by your browser, will trigger the /render 
phase/. This in turn renders the whole component tree. "Why redirect", 
you might ask. Well, this simply avoids that the same callback will be 
invoked again if you hit your browsers reload button. Whenever you hit 
on reload, this will only trigger a /render phase/ event.

From:
http://www.artima.com/forums/flat.jsp?forum=123&thread=96454

This would certainly be desirable behavior in Tapestry. I know there was 
some recent discussion about this, though I was a bit out of things for 
the past few weeks.

Thoughts?

Jamie

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org