What's the "general" use case ? There are a bunch of simple different things you can do right in the current scheduler to achieve that goal.... - schedule the same with different start_time(s) - queue the first with enabled=True and the following with enabled=False with a callback that flips the enabled bit for the next one - use an external "lock" record to coordinate - use a task that coordinates "subtasks" (always flipping the enabled bit) - etc etc etc
TBH, I see other things as useful for a lot of cases (i.e. tasks dependencies, e.g. task A needs to run before task B)....right now this feels like a corner case. It's also a bit difficult to implement without external tables, but that's another story....if it's useful we'll make it work ^_^ -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
