On Sunday, June 23, 2013 3:31:26 PM UTC+2, Apoorve Mohan wrote: > > Why do i have to run it separately? Ain't there any other method so that i > just specify the number of workers and as my application starts they are > automatically created/started? > > The scheduler process (i.e. an outside-band queue processor) kinda HAS to be run outside the normal web2py environment. The whole idea behind a queue processor is so different from the usual web environment that it has to be managed as a totally different process.
> If there is no such thing provided by web2py then I want to know how safe > it is to fire threads from web2py application from db callbacks? And are > there any thread pools provided by web2py? > > you can't fire safely threads from your db app (this is true in ~ every web environment). This is because the web environment is enginered towards "something" being fired for every "real web request", and that "something" is managed by a webserver in such a way that is safe to be managed whenever a real web request comes in. if you want, e.g., to have a long running process that doesn't take away resources from your web app, you have to manage it outside apache or similar programs. -- --- 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/groups/opt_out.
