Em Wed, 15 Oct 2008 10:21:39 -0300, Lubor Gajda <[EMAIL PROTECTED]>
escreveu:
The main problem here is not definition of conversation scope, but
specification of conversation boundaries (when the conversation should
start and when it should end and release all objects associated with
conversation scope). This mechanism should be as simple and user
friendly as possible
(all third party implementations I've seen so far are quite verbose in
this point).
What implementations? Any Tapestry-related one?
I agree that Tapestry is amazingly flexible framework that allows you
modify it's internal behaviour if you need it.
Not just modify internal behaviour, add new behaviour too. ;)
However, I also think that
conversation support is so common requirement (each nontrivial web
application needs it) that it should be supported out-of-the-box.
That's a good point.
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
Consultor, desenvolvedor e instrutor em Java
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
