If you don't explicitly "forget" the session, the session file will lock on each request, so subsequent requests will be blocked. Maybe you could forget the session on requests that don't need it and just keep it for requests that do need it (i.e., form submissions).
Note, to immediately unlock the session file, you need to do session.forget(response), not just session.forget(). Anthony On Thursday, August 25, 2011 2:14:54 PM UTC-4, G wrote: > > I tried session.forget() but found that forms submitted by ajax in > components don't seem to work without a session, so that won't work in > my case. > > I also tried removing the SQLite db, it may have helped some but I'm > still testing. > > Thanks again for the suggestions > > On Aug 24, 4:18 pm, Michele Comitini <[email protected]> > wrote: > > Try session.forget() and see what happens > > > > mic > > > > 2011/8/25 G <[email protected]>: > > > > > Thank you for the suggestion. I made a test application that used no > > > database accesses (no auth and randomly generated data). It showed the > > > same behavior, so I do not think it is the culprit. In addition, since > > > the application is monitor only, the real application only reads from > > > the database, which I hope would not impose a transaction lock. > > > > > G > > > > > On Aug 24, 3:20 pm, ron_m <[email protected]> wrote: > > >> You also need to consider the database type used by the application > for the > > >> model. The SQLite database has a transaction lock which will cause the > > > >> application to look like it is single threaded if the database is held > in a > > >> transaction pending state while the background work is performed. > > > >
