On Fri, Dec 19, 2014 at 2:20 PM, Andrew Greene <[email protected]> wrote:
> Are there any risks/cautions around creating tasks in a push queue with an > ETA of say 1 month or 1 year or even longer from now? > > +1 to Nick, and I would also add that having tasks sit in queue for a long period of time can make future updates to your code difficult, since you need to handle the "new" tasks and also the "old" tasks that may use a different set of parameters. If you need to enqueue tasks and have them sit for a long time, store the task info in Cloud Storage/Datastore/Cloud SQL, then have a cron job that loads soon-to-be-executed tasks into the task queue. ----------------- -Vinny P Technology & Media Consultant Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
