Unfortunately, it isn't possible to iterate over the entire blips in a wave now. When we send your robot information about an event, we send it a particular context, and that context may contain a parent + some children/siblings, but the context is not guaranteed to contain all of the blips in the wave. In our next revision of the API, we will let developers specify that they want "all" the context, and they can then iterate through all the blips. The context will not default to "all", of course, as that is a lot of information to send to developers that don't necessarily want it.
Please stay tuned to the blog and forum for updates. On Dec 10, 9:06 pm, Kartik Bansal <[email protected]> wrote: > *** Apologies if this question or a similar one has been asked before in > which case please direct me to its archive location *** > > I am building a robot using Java Client Library which parses the content of > entire wave and stores it in a external to be processed later. Whenever, a > BLIP SUBMITTED or BLIP VERSION CHANGED event triggers, my robot has to read > the entire content of the wave and store it in a external file. > > Any pointers on how i can do this? > > Thank you -- 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.
