Agreed - I also nominated this solution in my April 25th & May 1 posts :) - cheers,
Colin On May 29, 11:37 am, Stephen <sdea...@gmail.com> wrote: > On May 22, 9:46 am, hawkett <hawk...@gmail.com> wrote: > > > > > So - in the scenario where the HTTP client (i.e. the task queue) drops > > the HTTP connection in an initial task execution - how does app engine > > prevent the recovery mechanism from executing the task a second time > > while the first is still running? > > No idea if it does this or not -- but one way it could prevent > concurrent execution is by only re-executing a failed task 31 seconds > or more after the failure. By this time, the original task will have > been killed off, even if it did not manage to return a failure/success > code. -- 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.
