Being able to examine the task queue, and release tasks manually--and in different order than they were queued--is proving quite valuable. It would be nice to keep this as an option when you add automatic execution.
Vince On Tue, Sep 8, 2009 at 2:42 PM, Max Ross<[email protected]> wrote: > Interesting. We were planning on getting rid of manual task execution so > that dev would completely match prod, but if your experience is shared by > others it sounds like we should consider leaving the door open for manual > task execution as well. > > Thanks, > Max > > On Mon, Sep 7, 2009 at 8:52 AM, Vince Bonfanti <[email protected]> wrote: >> >> Perfect! At least for initial debugging, that's actually better than >> having the tasks execute automatically--it makes it easier to see >> what's going on with multiple tasks being queued. >> >> Thanks. >> >> On Sun, Sep 6, 2009 at 7:05 PM, Max Ross<[email protected]> wrote: >> > Hi Vince, >> > >> > In order to get the task queue into the 1.2.5 release we had to take a >> > shortcut with the local development environment. Tasks execute >> > automatically in production but not locally. However, in the local >> > environment you can kick off your tasks manually by visiting the task >> > queue >> > admin console page, accessible via a link off of >> > http://localhost:8080/_ah/admin >> > >> > We thought we had this properly documented but it appears we do not. >> > I've >> > filed a bug and we'll get this taken care of quickly. >> > >> > Sorry for the trouble. >> > >> > Thanks, >> > Max >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en -~----------~----~----~----~------~----~------~--~---
