Hi Stephen, In the SDK dev server, the task queue's tasks must be triggered manually. If you visit localhost:8080/_ah/admin/queues, you can see a list of queue names with a "flush" button to cause all enqueued tasks in that queue to be executed. Part of the reason for having a manual trigger for execution is to prevent runaway scenarios as you describe. In the SDK you can step through each "generation" of tasks and watch for endless or exponential triggers.
Happy coding, Jeff On Sun, Jun 21, 2009 at 5:27 PM, Stephen Mayer <stephen.ma...@gmail.com>wrote: > > So now that we have the task queue ... how do we test it in our > sandboxes? Or perhaps I missed that part of the documentation ... can > anyone clue me in on testing it in a place that is not production (I > wouldn't want a queue to start some runaway process in production ... > would much prefer to catch those cases in testing). > > Thoughts? > -Stephen > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
