Hi, It depends on your actual application. One method is to use some type of counter that is updated when the task runs, just append the current count to the task name. In some applications there might be a 'natural' counter you could use, such as a revision count on the entity you're updating.
Another method is to use a timestamp rounded to whatever unit you need (such as the next five minute mark). Of course, the timestamp method is generally less reliable since the clocks may not be exactly in sync. You can also use a memcache based counter + rounded timestamp, this is a decent method since the counter gets incremented when the task runs, and the timestamp is increasing in case of a cache miss. Robert On Fri, Feb 18, 2011 at 18:49, Seven Days <[email protected]> wrote: > Thanks Robert. > Your response has solved one of my problems but highlighted another. I had > mistakenly thought the task name would be available as soon as it executes, > and therefore the name could be used as a key to ensure only one of that > task is queued at a time. Do you know how I can achieve this? > > -- > 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.
