The latest news surrounding Google Wave is the release of a prototype server for the Google Wave Federation Protocol that allows developers to set up their own wave services. In essence, Google has released a federation port for Google Wave’s developer instance, allowing developers to start working with federating waves against the Google Wave Sandbox.
The news was announced on the Google Wave Developer blog, with additional details about the release:
When we first unveiled Google Wave a few months ago, one of the fundamental concepts we discussed was the vision for wave as an open communications protocol. We are happy to announce that the developer instance of Google Wave is now available for experimental interoperability testing with other wave providers. This means that if you are interested in building a service that uses the Google Wave Federation Protocol, you can begin prototyping with a tool like FedOne against WaveSandbox.com.
The news continues to highlight Google’s efforts to open up Google Wave as a new model for communication and collaboration. The release of the prototype server comes less than six months after Google Wave as initially previewed at the Google I/O conference, and about a month after Google Wave was opened up as a public preview to select users. There is a Google Wave API that has been available since the developer preview was released at Google I/O as well (our Google Wave API Profile).
Google has set up several resources for developers interesting in experimenting with the prototype server, including updated documentation for the Google Wave conversation model, installation instructions, a Java-based testbed client called FedOne, and EchoeyAgent, a simple “agent” for FedOne that echoes data back to a wave provider. Additional details for the installation process (and potential issues) have been posted to the Google Wave discussion group.
The installation relies on several dependencies, including the OpenFire XMPP server (or equivalent XMPP server) and Java 6. It should come as no surprise, that the instructions lean towards installation on Linux (though other operating systems are “likely” to work as well). We’re looking forward to seeing where all of this goes, as there is the potential for a new ecosystem of wave providers to emerge in the near future.