Thanks for the feedback, everyone. We are now working on describing the operations, and figuring out what the final operation set will be.
@cmdskp - Dynamic de-registration should be possible. On Sat, Nov 7, 2009 at 7:01 AM, cmdskp <[email protected]> wrote: > > About the future "allow Robots to initiate actions via JSON-RPC, > rather than simply respond to events", I have been thinking that it > would be good for a robot to be able to dynamically register and > deregister from events. > > This would allow a robot to manage it's quota during busy periods > (e.g. deregistering from character changes to only responding on > BLIP_SUBMITTED) and then back again when it is less 'busy'. > > On Nov 6, 9:28 am, qMax <[email protected]> wrote: > > I agree with Smola. > > > > This draft covers no more then we can see in our appengine robot logs. > > > > Details of each event and operation parameters are very desirable. > > (among other use, this will allow us to play new events/operations, > > not yet covered by API methods) > --~--~---------~--~----~------------~-------~--~----~ > 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]<google-wave-api%[email protected]> > For more options, visit this group at > http://groups.google.com/group/google-wave-api?hl=en > -~----------~----~----~----~------~----~------~--~--- > > -- 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.
