Feeds

Google open sources Wave gravy

Operational transformation

Providing a secure and efficient Helpdesk

As it strives to replace email, Google has open sourced two chunks of its new-age communications platform, Google Wave.

Unveiled to a standing coder ovation at the Google I/O developer conference in late May, Google Wave is a (still-gestating) web platform that crossbreeds email with IM and document sharing, exhibiting a particular talent for near real-time interaction. Hoping to promote its use across the net, Google intends to open source the platform's underlying protocol and the "lion's share" of its client and server code.

With a post to the official Google Wave Developer blog, the company took its first steps towards fulfilling this promise, opening up the "Operational Transform" (OT) code that underpins the platform as well as a simple client/server prototype that uses the Wave protocol.

Wave's real-time talents spring from Google's OT code. Based on the operational transformation architecture introduced by the Jupiter Collaboration System developed at Xerox PARC, it puts all shared content in the hands of the server. The client can't edit content without first sending an operation to the server - and it can't send an operation unless the server gives the OK. That way, the server needn't keep multiple copies of content for each client.

"The OT code is the heart and soul of the collaborative experience in Google Wave, and we plan that code will evolve into the production-quality reference implementation," Wave engineers Jochen Bekmann and Sam Thorogood wrote in announcing the open sourcing of the code.

Meanwhile, the client/server prototype is meant to encourage experimentation with Wave's underlying communications protocol, based on the open XMPP (Extensible Messaging and Presence Protocol) standard. Dubbed the Google Wave Federation Protocol, it's already published as a draft specification and freely licensed through the Creative Commons alongside the Google Wave APIs.

Both the protocol and the OT code have been updated since Google I/O, with Google saying the OT code has advanced beyond the algorithm implemented by the production servers used by the few thousand Google employees and outside developers currently testing the platform.

In all, Google has opened sourced nearly 40,000 lines of Java code, all under the Apache 2.0. license. ®

Internet Security Threat Report 2014

More from The Register

next story
Microsoft on the Threshold of a new name for Windows next week
Rebranded OS reportedly set to be flung open by Redmond
'In... 15 feet... you will be HIT BY A TRAIN' Google patents the SPLAT-NAV
Alert system tips oblivious phone junkies to oncoming traffic
Apple: SO sorry for the iOS 8.0.1 UPDATE BUNGLE HORROR
Apple kills 'upgrade'. Hey, Microsoft. You sure you want to be like these guys?
SMASH the Bash bug! Apple and Red Hat scramble for patch batches
'Applying multiple security updates is extremely difficult'
ARM gives Internet of Things a piece of its mind – the Cortex-M7
32-bit core packs some DSP for VIP IoT CPU LOL
Lotus Notes inventor Ozzie invents app to talk to people on your phone
Imagine that. Startup floats with voice collab app for Win iPhone
'Google is NOT the gatekeeper to the web, as some claim'
Plus: 'Pretty sure iOS 8.0.2 will just turn the iPhone into a fax machine'
prev story

Whitepapers

Providing a secure and efficient Helpdesk
A single remote control platform for user support is be key to providing an efficient helpdesk. Retain full control over the way in which screen and keystroke data is transmitted.
Intelligent flash storage arrays
Tegile Intelligent Storage Arrays with IntelliFlash helps IT boost storage utilization and effciency while delivering unmatched storage savings and performance.
Beginner's guide to SSL certificates
De-mystify the technology involved and give you the information you need to make the best decision when considering your online security options.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.
Secure remote control for conventional and virtual desktops
Balancing user privacy and privileged access, in accordance with compliance frameworks and legislation. Evaluating any potential remote control choice.