On Jan 18, 2011, at 5:41 PM, ae wrote: > > On Jan 18, 11:22 am, Jonathan Lundell <[email protected]> wrote: > >> When you say "anyone associated with the thread", do you mean other requests >> using some shared, locked resource (like the session)? Or something else? > > Browser sessions seem to get associated to a thread. As long as that > thread is busy the user won't (and anyone else who's session is > assocated to that thread won't) be able to do anything else. This > mostly seems like a security precaution and is good.
Each request runs in its own thread. Users don't share sessions, so session serialization won't block other users. Database serialization could, though. On the whole, I think you're better off using JavaScript to make this kind of thing asynchronous. Better user experience, too.
