Did you test in a production environment (example behind an apache/other server calling web2py via wsgi as described in the deployment recipes chapter) or just using the built-in web2py server on your dev machine?
The difference is that apache will certainly be able to handle multiple simultaneous requests, even long running ones until it runs out of allocated resources. Not sure if the built-in rocket server can do that or if it only handles one request at a time. If you are unable to run multiple requests even behind a production server, then check if the processes are locking each other (trying to get locks on the same file, locked because they are updating/reading the same database tables and keeping locks on them, etc) -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
