Under the hood, Google Wave robots operate by receiving events and sending
operations via JSON messages at specified URLs. Our robot client libraries
(in Java and Python) wrap on top of that wire protocol and expose the events
and operations as classes and methods.

When we first launched the robots SDKs in June, we received feedback about
various issues with this underlying protocol. These issues bubbled up to the
client libraries, and often made it harder to use the client libraries.

As mentioned in the "What's coming" forum post a few months ago, we have
been working on the next version of the wire protocol. We have now come up
with a protocol that we think is much cleaner and will make development
easier.

We have published a draft of this new protocol here:
http://code.google.com/apis/wave/extensions/robots/protocol.html

This protocol will form the basis of future client libraries, so once we
feel confident about this protocol, we will release client libraries that
use it.

If you are a developer thinking about writing a client library in your
language of choice (like Ruby, PHP, etc), then this document will be of
great interest to you.
If you are a developer that uses our current robot APIs, then this document
may help you understand the mechanisms of robots better, and prepare you for
future client libraries to come.

Please take a look and give us your feedback, both on the protocol itself
and on the documentation.

Thanks!

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to