The Tapestry rules, as I understand them, are when a request comes in,
it can access the visit (session) and that object is associated only
for that request (which is running in a thread) for the duration of
the request. If you have your DataContext in the visit only, there
should be no spill over to other requests. Tapestry is supposed to
handle ensuring the proper request is associated with the proper visit
object. I'm not certain how/where you were seeing the streams
crossed.
/dev/mrg
On 9/29/06, Øyvind Harboe <oyvind.harbo..ylin.com> wrote:
> On 9/29/06, Andrus Adamchik <andru..bjectstyle.org> wrote:
> > DataContext is not thread-safe, as it is intended for access by a
> > single user.
> >
> > DataDomain and the rest of the stack underneath the DataContext is
> > thread-safe.
> >
> > If a there is a chance of multiple threads belonging to the same user
> > to access the context (and its DataObjects) simultaneously, you'll
> > have to synchronize manually.
>
> Thanks for the clarification. I can't really see how Cayenne would
> have "solved" this problem.
>
>
>
> --
> Øyvind Harboe
> http://www.zylin.com
>
This archive was generated by hypermail 2.0.0 : Fri Sep 29 2006 - 12:12:37 EDT