Google Open Sources Wave Protocol Implementation

eldavojohn writes "Certainly one of the most important steps in adopting a protocol is a working open source example of it. Well, google has open sourced an implementation of the wave protocol for those of you curious about Google's new collaboration and conversation platform. It's been reviewed, skewered and called 'Anti-Web' but now's your chance to see a Java implementation of it. The article lists it as still rapidly evolving so it might not be prudent to buy into it yet. Any thumbs up or thumbs down from actual users of the new protocol?"

Comments

Re:OK, now what does it do?

[jtdennis]

I've read reviews of it as real time collaboration. Think of it as private e-mail, IM, and document collaboration all in one system.

Re:When does the Litigation Start?

[d3l33t]

I for one feel bad for the helpless telecoms. They have done everything in their power provide nothing but exceptional service to customers over the past 30 years, including protecting our privacy and investing in infrastructure ~/sacrasm. Regardless of 'infringing' business models, we should be rejoicing the opportunity to compliment the current, and broken, communication model. By providing an alternative protocol with specific functionality it's not replacing current technology, simply enhancing it. Let's just hope it's not a product of the PR machine.

Re:Oh, well, if there's a Java implementation

[Smegly]

It might be pro-GoogleOS. I would not be surprised if it becomes a communication hub for Google's netbook OS.

It's too early, but...

[SebaSOFT]

I think that every web developer that misses this out, will pay it hard.
Experts say that true innovations are hard to detect. I would say, keep an eye on this, or you will regret it.

Re:My feelings on Wave

[dragonworks2050]

But isn't that what Chrome OS is for? Ultimately, Google wants the browser and the OS to be identical.

Re:My feelings on Wave

[jesset77]

Why develop for three platforms and let geeks port that to many when you can develop as open source for one platform (DHTML) and actively encourage the geeks to port that to 3, and then to many?

Hell, if I worked at Google the last thing I would want would be to get involved in GNOME/KDE turf wars, piss off apple fanbois if it doesn't look precisely like a macintosh app or really develop anything for the Windows desktop. Like, ever. So instead, Google puts it on the Web where everyone can get at it from any modern platform (even/especially smartphones, and if you want a native copy then you or some hobbiests are free to write one (and thereafter support it :P)

Seriously, do you recall their last attempt at a Jabber desktop application, Gtalk? It even worked well, but then they dropped it like a bad habit in favor of the web-based version.

Additionally, one of their main design goals was to make Wave conversations embeddable into web pages. They would like this to be used for CMS, to replace forums, to replace blog comments, essentially they wish people to mash up Wave content with their own web pages. If they focused their deployment first to the desktop, they would miss out on that opportunity.