Explicit task naming is a technique to prevent "fork bomb" which is unwanted creation of duplicate tasks. You do not have to name your tasks. However If you have a long running task chain you should think of how you are going to prevent fork bomb. The problem arises when something inside your task fails and task is re-tried. Each time a task is retried is is going to fork another task. You can see how this gets out of control quickly. This is not just theory. I have seen it many times myself.
-- 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.
