Another way you can approach this problem is by listening to the blip submited event, and measuring the incremental diffs between each revisions. You won't be able to access revision data before the robot has added, but you can measure everything else since.
-SDr On Fri, Oct 23, 2009 at 8:27 PM, Austin Chau (Google employee) < api.aus...@google.com> wrote: > Currently blip revision data is not available to any of the API. Feel free > to file an feature request for it. > > http://code.google.com/p/google-wave-resources/issues/list > > Austin > > > On Fri, Oct 23, 2009 at 9:18 AM, Leitzler <leitz...@gmail.com> wrote: > >> >> I've been searching for a way to access the history of a wavelet from >> within a robot, is it possible using the Java Robot API? >> >> I am trying to write a robot that creates a summary in the root blip >> that tells how many words each participant have been deleted through >> the history of the current wavelet. >> >> Any ideas? >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-api@googlegroups.com To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en -~----------~----~----~----~------~----~------~--~---
