On Tue, Jun 26, 2012 at 7:31 AM, Michael MacFadden < michael.macfad...@gmail.com> wrote:
> All, > > I have some questions on the Wave APIs in terms of what each one is for, > and what they offer. I believe I know the answer to some of these but want > to get opinions from the list before documenting these. > > 1) What are the APIs we want to offer to the community? > > 2) What is the Robot API used for? > > The Robot API allows automated processes to take part in a Wave just like humans would, a Robot has it's own Wave(?) address. The API comes in two flavors. The passive API is an event-based API where a Robot can subscribe to events, such as adding a new participant to a Wave or changes in a blip. The Robot will then be notified of such events via an HTTP request. The response to this request can then contain operations that will be applied to the Wave. In the Active API the Robot does not act based on events it receives from the Wave Server but rather initiates an action on its own accord. It sends an HTTP request, much like the response in the Passive API to the server, which contains any operations that the Robot wants executed. The Active API uses OAuth for authentication. > 3) What is the Data API and what is it used for? > The Data API is similar to the Active Robot API but allows you to programmatically access the data of a real User instead of a Robot. 3-legged OAuth is used for authentication. > > 4) Is there any code for federation that is reusable? > > 5) Is there any code for the client server protocol that is reusable? > > 6) Any other ideas? > > Thanks. > > >
