On Friday, September 18, 2015 at 12:01:30 PM UTC-7, Niphlod wrote: > > imho the scenario isn't clear. Why having a sleuth of workers waiting for > tasks enqueued by your app is not viable for multiple users ? > > On Friday, September 18, 2015 at 8:14:31 PM UTC+2, Phillip wrote: >> >> If I understand, using the scheduler in my case would only be a viable >> option for my own processing purposes, not multiple users. If so, it >> appears that my only option would be to export a desktop version of the >> interface to be used for this processing. If I am offtrack here, please let >> me know. Otherwise, any other comments are welcome. >> > Is there some confusion regarding "to have a process (or multiple ones) NOT managed by the webserver"? It should be pointed out that these processes are run on the server (because they need access to the resources) and usually owned by the same user that owns the web2py process. There won't be access to session variables or a req variable, but there is the pvars and pargs in the task DB which the queuing controller can fill in from its session and req, right?
<URL:http://web2py.com/books/default/chapter/29/04/the-core#queue_task-> /dps -- 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.
