On 11/30/05, Jason Chu <[EMAIL PROTECTED]> wrote: > On Wed, Nov 30, 2005 at 09:52:14AM -0500, Kevin Dangoor wrote: > > A nice workaround, I think, will be to implicitly start a Transaction > > for each request, which is something we've talked about before: > > http://trac.turbogears.org/turbogears/ticket/80
> This implicit behaviour will happen before Identity gets a hold of > anything, right? I'm not quite sure how it works, but our code ends up > checking turbogears.identity.current.user quite a bit and if > turbogears.identity.current.user was selected outside of the current > transaction then 'turbogears.identity.current.user ==' won't match any User > objects that are grabbed within that transaction. This would *have* to happen before Identity does its thing. > I don't remember if current is set as part of threadLocal (and if it is, > does that mean it's persistent across requests?) or if it's just updated > every time the user makes a request. This should change (and I think I've said this before) to storing the identity info in the request. This information really is request specific and not specific to a thread... Kevin
