it doesn't depend on web2py, but on what server is serving the web2py application (that is a normal wsgi app). Web2py ships with rocket as the default webserver (meaning, when you start it with web2py.py you're using rocket to serve the web2py code). Rocket is a threaded webserver, so yes, every request gets its own isolated thread to run into. Rocket uses a pool of threads, though, so it launches threads up to a maximum and then recycles them as needed. NB: this is just speaking of rocket. if you use, e.g., uwsgi to run web2py, then the things could be different (i.e., usually uwsgi forks a process for every incoming request).
On Friday, August 9, 2013 8:49:59 PM UTC+2, Mark Finkelstein wrote: > > I was wondering, does web2py launch a separate thread for each web2py > request to respond? > -- --- 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/groups/opt_out.
