Thanks for the feedback, the session._unlock(response) call did the
trick.
It does raise a question for me though. Is it so uncommon for people
to hit the server with a couple of lengthy ajax calls from a single
page, that the solution to allowing them to run them in parallel is
not really adverti
There are two possible causes for locking.
session locking. You can unlock them with session._unlock(response)
sqlite locking. Nothing you can do other than not using sqlite.
On May 24, 8:16 am, Candid wrote:
> I might be completely wrong, but I think the problem is that web2py
> locks the sess
I might be completely wrong, but I think the problem is that web2py
locks the session file while executing controller's actions, so two
simultaneous requests within the same session are processed one by one
sequentially.
On May 24, 8:37 am, eddie wrote:
> I have found this recent thread:
>
> http
I have found this recent thread:
http://groups.google.com/group/web2py/browse_thread/thread/80941011f6407703/5047c1417c35b125#5047c1417c35b125
But I'm still not entirely sure what the net result is for multiple
controller calls, via ajax or otherwise.
What exactly does the -n option allow in ter
4 matches
Mail list logo
