Thank you again for this precious information. :)
Richard On Fri, Apr 19, 2013 at 10:59 AM, Niphlod <[email protected]> wrote: > they both process tasks. > the "line" is what I described in the previous post: if you need rapidly > firing jobs, better stick with rq, if you need periodic jobs, rq setup > needs a new component. > The only other "cons" on the rq list (but is negligible) is that it works > only with redis and on unix. > Managing other things that web2py's scheduler has, as requeueing failed > tasks, etc etc can be accomplished with rq too and custom code (i.e. > they're not native to rq, but not difficult to implement) > > For "once in a week" requirement, they are both definitely *not* the tool > that I'd use. > > > -- > > --- > 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. > > > -- --- 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.
