My basic interpretation: The scheduler shouldn't be managed by the webserver (shouldn't be controlled by user requests) which could basically create zombie processess and / or will drop long-running processes.
If you see no reason the scheduler shouldn't work for this purpose (while preventing long-running processes from dropping (what I thought the timeout feature was for))? Could there be scalability issues with too many users attempting to run too many processes (on GAE for instance)? -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
