Thanks, David. I'll play around with the cron job idea, but it looks like I'll have to compromise and figure out a different behavior for the robot.
- Daniel On Nov 8, 2:19 am, David Nesting <[email protected]> wrote: > On Sat, Nov 7, 2009 at 7:14 PM, Daniel Rothenberg > <[email protected]>wrote: > > > adding text to the document it's working in, but I've noticed that it > > doesn't look like Wave is updating the document until after > > OnBlipSubmitted() completely finishes. > > Robot events are simply HTTP requests. The wave server makes an HTTP > request to your robot, provides all of the details of the event in the > request, and your robot returns an HTTP response that contains the > operations your robot wishes to perform in response to that event. You only > get one set of operations per event, and all of those must be returned and > processed at once. You can't sleep between incremental updates, because the > incremental updates are all sent as one set of operations, and you're just > delaying when those operations get sent back to the server. > > > Is anyone familiar with a technique I can use to get my robot to > > incrementally add the words of the question to the document it's > > writing and have the document visibly change with each addition? > > You could use a cron job for this: > > http://wave-robot-python-client.googlecode.com/svn/trunk/pydocs/wavea... > > I would worry that the timing of this may not be consistent enough at the > rate you're likely to want the blip updated. > > David --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Wave API" 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-wave-api?hl=en -~----------~----~----~----~------~----~------~--~---
