Somehow I missed that it's a draft only. I thought the protocol already supported it, so I just added the event to the Python client lib in waveapi.events. I guess I will have to listen for other events and incur the additional traffic load for now. Which event should one use: BLIP_SUBMITTED, DOCUMENT_CHANGED, ..?
On Nov 17, 5:15 am, cmdskp <[email protected]> wrote: > Ah, found where I read it - the draft version of the next Robot API > here: > > http://code.google.com/apis/wave/extensions/robots/protocol.html > > On Nov 17, 2:45 am, cmdskp <[email protected]> wrote: > > > GADGET_STATE_CHANGED does not exist currently - but has been mentioned > > by Google as coming in a future version of the API, AFAIK, this hasn't > > been released yet. > > > Possibly I read about it on the Wave API Issues. > > > On Nov 16, 9:58 pm, qMax <[email protected]> wrote: > > > > And GADGET_STATE_CHANGED is not in current API neither in java nor > > > python. > > > Where did you found it ? > > > > On Nov 17, 1:02 am, hcvst <[email protected]> wrote: > > > > > Hi, > > > > > my bot's capabilities.xml states that it is interested in > > > > GADGET_STATE_CHANGED events. I've upped the bot's version after adding > > > > this event to the ones it's interested in, yet looking at the GAE logs > > > > my bot does not seem to be notified. > > > > > Is this event not supported yet? > > > > > Thanks, > > > > HC > > -- 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=.
