Sweet- looking forward to using the API. Schema changes a pain but done for right reasons. Can you give more explanation of the immediate=True param?
As for patterns- a basic event calendar would be good demo Thanks for the great work Niphlod On Sat, Feb 23, 2013 at 1:21 PM, Niphlod <[email protected]> wrote: > resuming historic thread. > Latest commits added a few features, and changed schemas a little (my > fault, sorry). > Now db schema complies with check_reserved=['all'], so should work in any > RDBMS out there: > - scheduler_run.output --> scheduler_run.run_output > - scheduler_run.result --> scheduler_run.run_result > - scheduler_run.scheduler_task --> scheduler_run.task_id > > New features: > - API available: .queue_task(), .task_status(), .resume(), .disable(), > .terminate(), .kill() > - W2P_TASK variable injected into tasks > - a new "immediate=True" parameter to queue_task in order to wake up a > "nothing to do..." looping worker > > The app on Github has been updated with all the new features (use web2py's > trunk, not stable). > > I'm planning to include also common patterns using the scheduler. As > always, feel free (or, should I say, compelled ? :P) to propose your "most > wanted" patterns (e.g. manage an email queue) > > > > -- > > --- > 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.
