Agree with Robert named tasks are the way to go. I have a similar requirements - have a long running state machine implemented as chained tasks. Once I worked out transactional issues and added "choke" points to prevent fork bomb it has been running ok for over 1 week now. Clarification, by "running ok" I meant that task flow is sustained in presence of occasional datastore and memcache errors. You task handlers and app as a whole should still deal with idempotancy issues arising from errors.
On Nov 21, 5:07 am, Remigius <remigius.stal...@gmail.com> wrote: > Ian, > > It does not look like there's a facility to look up queued tasks in > the task queue API. Instead you could use a heartbeat in the data > store (i.e. save an entity with a timestamp each time the task queue > task runs) that is checked by the cron job. > > Cheers, Remigius. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
