It is good that it is not possible. Otherwise you could not use this feature to prevent fork bombs and you would need to implement the same thing yourself.
If you do not need that feature, do not name the task. Or, name the task but if you get a tomb-stoned task error, increment the task's name and try to enqueue it again. Robert On Tue, Nov 2, 2010 at 10:49, andreas schmid <[email protected]> wrote: > hi, > > > i don't really understand why a task name has to be unique forever on my app. > i think it would be a lot better if a task can be add to a queue if its not > already in there and as soon as the task is done another process could add it > again with the same name. > > or am i doing something wrong in my app and this is possible? > > -- > 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. > > -- 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.
