On Monday, February 25, 2013 10:59:28 PM UTC+1, Yarin wrote: > > 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?
The app has some docs about it, but to make a tl;dr of it scheduler checks for new tasks every 5 loops. So, worst case scenario, you can have a timeframe of heartbeat*5 seconds from the moment you queued the task to the moment it gets ASSIGNED. If you set the worker status to PICK (only to the ticker, the one with is_active=True) as soon as he reads the status (so, every heartbeat seconds) and see "PICK" it will try to assign the tasks without waiting for the 5 loops. immediate=True to queue_task just coordinates all the bits: it inserts the task and set to PICK the ticker. > As for patterns- a basic event calendar would be good demo > Can you elaborate on that a bit ? > > -- --- 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.
