On Sat, 2002-07-13 at 12:25, Howard M. Lewis Ship wrote:
> The problem is that you have to understand a lot about Tapestry to get it to
> work right; other than that, it's fine (speed is not an issue).  But the
> concept of repeatable renders (which, in turn, is which properties must be
> persistent so as to re-render the page a second time), it difficult to
> express.

I use Action extensively, and so far it seems to work, but I'll admit
that I don't understand the finer points of persistent properties -- in
fact I don't even understand why there is a distinction -- is it to do
with a single page instance being used by several sessions?

How can one use Direct as a substitute for Action? The only way I can
see to do that is to maintain my own Map of keys and listeners.

Tom

-- 
"Optimism is a duty. The future is open. It is not predetermined. No one
can predict it, except by chance. We all contribute to determining it by
what we do. We are all equally responsible for its success."
  Karl Popper



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer

Reply via email to