You should use the scheduler. When you run web2py in production you may run into problems because the web server controls wich processes to kill.
On Aug 23, 3:50 pm, Tkey <till.keyl...@googlemail.com> wrote: > Hi, im new to web2py and i want to port some of my python scripts to a > webserver-enviroment, while some of them nee user interaction (f.e. aceesing > results in a database) and some of them should simply run server-side in the > background (f.e. collecting data every hour). I´m using the > multiprocess-module pretty often in those "server-side" scripts,but when i > copied them 1 to 1 into the web2py controller section (i don´t know if this > is the appropriate place for such server-side scripts) and executed them via > a url-call, they just don´t work (they do in a "normal" shell > enviroment)...instead, several processes of web2py are executed.. > > So, in general, can´t you use the multiprocess module in web2py (I´m using > it mainly to download a lot of websites in parallel/API calls on twitter > etc., which is much faster than a single process)
