Andrus Adamchik wrote:
>Probably not a good idea (unless your whole app is read only). Normally
>each user session must have its own independent DataContext. In Tapestry
>terms "session" is represented by "visit", so you can simply create a
>DataContext in a Visit class.
>
>
Good point...I guess haven't thought it through all that well. I'll
extend the Visit class and that'll be that.
Thanks for the advice.
This archive was generated by hypermail 2.0.0 : Sat Feb 26 2005 - 09:28:52 EST