For a little more than a month, Google threw a full-scale test (they speak about 100 000 silly billy testeurs) of the deck of centralised communication, Wave. After a big frenzy of hunt for invitation, the bellows fall again little by little: they really have a feeling that there is something to pull of this aggregate of tools become 'real time ', but they still do not know what. They see appearing of many archetypes (translation real time, connection with motives), but few very concrete things. It will be necessary for it to wait to attain a critical mass (if several firms decide for example to replace the entirety of their tools of communication with Wave) but also count on the community to explore the possibilities of extension of Wave and to offer delightful robots.

Nonetheless, the tool of Google stirred our curiosity, mainly thanks to its opened architecture and to its possibilities of extension.

Three protocols, two IPA - INTERNATIONAL PHONETIC ALPHABETS

Google Wave Federation Protocol

It is all interest and heart of the product of Google there. Indeed, thanks to this new protocol opened and standardised, the accommodation of a server Wave can be made independently of Google. And it is the nerve of war for the firm there: contrary to Google Docs, which centralises documents about a platform accommodated at the editor, the aspect opened by the protocol of federation between servers Wave is going to allow to every firm to keep workmanship on its Waves, and on the documents which compose them. Some people already imagine the very nice Utopia of a passing client command his supplier via common Wave, managing complex processes (passage of order, dispatch of automated estimate, workflow human being of validation and automatic invoicing).

If they are furthermore interested near in this protocol, they note that it is about an extension of the well-known protocol XMPP (before called Jabber). Google leant on the mechanism of extension of this protocol (XEP 114) to reinforce especially the security of exchanges inter-servers but also the authentication strong in an user to his Waves.

In a diagramme, this protocol leans on mechanisms of Gateway / Proxy. Every server has Gateway, who takes care of local modifications of every accommodated Wavelet. Cette Gateway pushes these modifications then towards Proxys of other servers participating in Wave.

This protocol being opened, you will be able to find a rich material on the site of Google, via and of many white papers.

And if you want to launch into experience, Google offers, outrages the server Wave of use for the silly billy, the prototype server implemented in Popular dance.

Protocol client-server

To interact with Wave, every participant must equip himself with a client. At the moment, it is there that the only one, the client web created by Google and available on https://wave.google.com / Wave / (or one of its encapsulations, as WaveBoard). The protocol which allows to exchange with the server Wave is not specified at the moment even, but .

The client web of Google is a HTML 5 application, developed with GWT. It announces with the following server a possessing protocol GWT, carried by HTTP.

The hope of standardization on the side of the clients is however tangible: the ProcessOne society accomplished .

IPA - INTERNATIONAL PHONETIC ALPHABET Robot and JSONRPC

Last protocol, and the not of slightest, the protocol which allows robots (for the fans of irc, they speak about club foot) to intervene in Wave. To be made, they use JSON-RPC, on HTTP.
These robots work on a factual programming. They are therefore in priori agnostics in relation to language. There is currently 2 IPA - INTERNATIONAL PHONETIC ALPHABET given by Google: one for Popular dance, which we will itemise in a next article, and .
Robots can interact with Wave (participants' addition, modification of the contents of Wave, dispatches of alerts) by being launched by internal events in Wave (arrived from a new participant, publication of text, launching by key word).

IPA - INTERNATIONAL PHONETIC ALPHABET Gadget

There is another way of enriching the functionality of Wave: gadgets. Gadgets are bricks of code (HTML + javascript), well-known of users of iGoogle, loaded into the client Wave. They are similar to those of the IPA - INTERNATIONAL PHONETIC ALPHABET OpenSocial, even if curiously this one is not officially compatible. The difference with the static gadgets is that gadgets Wave take advantage from the aspect ' live ' of Wave and can interact with this one. They include a state management, know the user in the course of visualisation and the linked users and integrate with the mechanism of playback.
We will come back also more in detail on the writing of gadget there.

Synthesis

To sum up these different protocols, the simplest is still to represent them on a diagramme.

source:

With extensions correctly thought and developed, Wave seems to be able to be a huge trump in the internal call of the firm.
Then, will you be the first to instal a server Wave in return for of your good old SMTP?