Just to clarify, I meant check for all markers at the end of each task to decide if the process ready for the next step. I agree with Nick, blocking is probably not the best approach.
On Mon, Jul 18, 2011 at 15:51, Robert Kluin <robert.kl...@gmail.com> wrote: > Hey Jim, > If you mean between a client and GAE maybe you'd find the Channel > API useful. If you mean between two tasks running on App Engine how > about using 'markers' that you can fetch. Then, once all are present > and in a 'completed' state, fire off the next step in the process. In > other words use a push pattern instead of a pull pattern. > > > Robert > > > > > > On Mon, Jul 18, 2011 at 14:43, Jim Mittler <chicago...@gmail.com> wrote: >> I have some patterns that I would very much like to try to implement >> in GAE, but I can't seem to get past a requirement to coordinate a >> signal between two tasks running in GAE. >> >> There seems to be no GAE mechanism to wait for an event without going >> into some sort of polling loop. Is there something maybe that I'm >> missing or is this just wishful thinking? >> >> Thanks!! >> >> -- >> 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. >> >> > -- 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.
