By the way, if you're doing task queue chaining or need complex workflows, check out Brett's Pipeline API:
http://code.google.com/p/appengine-pipeline/ An alternative is Fantasm: http://code.google.com/appengine/articles/fantasm.html I personally found Fantasm a bit more accessible for the types of simple workflows I need (sorry Brett!). They're both great libraries, though. Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine On Fri, Mar 11, 2011 at 11:24 AM, vlad <vlad.troyan...@gmail.com> wrote: > 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 google-appengine@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. > -- 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-appengine@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.
