Google Wave API

The Google Wave API allows developers to use and enhance Google Wave through two primary types of development:

• Extensions: Build robot extensions to automate common tasks or build gadget extensions to provide a new way for users to interact
• Embed: Make your site more collaborative by dropping in a Wave
  

  Google Wave API

Google Wave is currently available in a developer preview as the APIs and product continue to evolve. Accounts on the developer sandbox will be given out to people intending to build with the Google Wave APIs prior to the public release.

The Google Wave API is an open platform allowing developers to extend the functionality of Google Wave itself, or extend other applications with waves. As a developer, you can think of Google Wave as three pieces:

• The Google Wave client application, the interface designed for users
• The Google Wave APIs, which are documented throughout this site
• The Google Wave Federation Protocol, the underlying network protocol for wave communication

Programming effectively using the Google Wave APIs requires understanding some basic wave concepts.

Understanding Google Wave Concept

A wave is a threaded conversation, The wave is a dynamic entity which contains state and stores historical information

A wavelet is a threaded conversation that is spawned from a wave. Wavelets serve as the container for messages, known as blips. The wavelet is the basic unit of access control for data in the wave. As well, all events that occur within the Google Wave APIs operate on wavelet level or lower.

A blip is the basic unit of conversation and consists of a single messages which appears on a wavelet.

A document is the content attached to a blip. This document consists of XML which can be retrieved, modified or added by the API. Generally, you manage the document through convenience methods rather than through direct manipulation of the XML data structure.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.