Massimo, if one thread/request locks the session file, can a second request unlock the file, or does it have to be unlocked within the same request that locked it? For example, let's say a page includes two components (via LOAD) -- if the request for component1 locks the session, can the component2 action then unlock the session, or will the component2 action have to wait for the component1 action to finish and release the lock? Thanks. Anthony
On Wednesday, March 23, 2011 11:02:06 AM UTC-4, Massimo Di Pierro wrote: > There are two things that may lock: one is the user session (you can > check it by opening two pages with two distinct browsers like firefox > and chrome); the sqlite database (that is how sqlite works). > > We cannot tell what is wrong in your case without a code example and a > workflow example. I am pretty sure there is no bug in tis regard. > > Notice that other frameworks that use cookie based sessions do not > guarantee session integrity therefore they do not serialize requests > from the same user. > > > > Massimo > > On Mar 23, 9:44 am, Ross Peoples <ross.p...@gmail.com> wrote: > > Unless there is some unknown trick, I was unable to find a way to make > this > > work, which is why I turned my script into a subclass of Process. Though > I > > do know Rocket can handle multiple simultaneous downloads at once since > it > > allows the browser to download multiple files from /static at the same > time. > > So maybe this is a web2py bug? > > > > But either way, a long-running script should be spun off into its own > > process for performance reasons.
