Ok. Everything is fine. Using task name will prevent multiple undesired new task chains but still you need to design task to be idempotent. I don't think that using task name will give you idempotent property. It will prevent one side effect of not being idempotent in a way that this effect will not explode but it will still exist. With task name you are dealing with a consequences instead to prevent causes.
We design our task to be idempotent and for task chaining we are using Tasks within transaction feature<http://code.google.com/intl/hr/appengine/docs/java/taskqueue/overview.html#Tasks_Within_Transactions> so that there are no undesired task chain forks. P.S. These workflow apis are nice but they exists only for python and we are using java version. GWT, Android and GAE app inside one great IDE (IntelliJ IDEA) and using one programming language is pretty strong motive for java. -- 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.
