it's generally a bad idea. webserver can kill your threads (or processes) that are hanging (like when launching a very long process you want to communicate with) without notice: they do to allow other requests to be served, and they kill zombie processes too.
That's why there's a plethora of outside-band async queue-based managers, meant to run outside the scope of the webserver. Web2py has scheduler.py, but that's just one solution. Feel free to expand your searches. On Monday, October 22, 2012 12:15:34 AM UTC+2, Tim Richardson wrote: > > Imagine I have a controller that uses multiprocessing to run something in > a different process, and then I want an ajax function that updates the form > communicating with the background job with a multiprocessing.Manager() . > I need to keep track of my manager per session. This is not going to work > is it? --
