I'm afraid that there is no guarantee that tasks execute once. The named task prevents it from being inserted a second time, but an enqueued task has "at least once" semantics.
Jeff On Fri, Jan 20, 2012 at 4:49 PM, AndyD <[email protected]> wrote: > Would a task queue work here? You could queue a task with a name that is > unique to the operation (e.g. leveraging some payment ID, in the example > case). If a task with the same name is already in the queue, or was in the > queue in the last 7 days, GAE won't queue it again. This gives you the > run-once, retry, and pruning of old tombstones (in this case, the task name) > automatically. > > Giving credit where due, this approach is taken from Dan Sanderson's > "Programming Google App Engine" book (O'Reilly). > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/VVq0iD0escIJ. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
