I'll say it once again: you need a scheduler to run out-of-band pieces of things (tasks) that ARE NOT embedded in the web-serving process(es). At that point you may as well process out-of-band tasks with a simple ajax call, and save yourself setting up the scheduler at all.
It's strongly discouraged to start ANY process inside the webserver (stderr/stdout clumsiness with wsgi, enforced timeout on the webserver, DDoS attacks, etc). Starting a python process inside a controller (even if it's the scheduler) has the same exact cons. The scheduler NEEDS (read: there is absolutely no valid reason not to) to be started as an external and independant process from the webserver: if you need it to be started when the server comes up, you NEED to use your system's "service" architecture (init.d, systemd, supervisord, windows service, etc) . Or, if you're using uwsgi, you can use its facility to spawn external processes (it's in the default installation script). -- 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.
