Return to Jive Software

Skip navigation
Currently Being Moderated
7

XMPP and Web Progress: Google Wave

Posted by Matt Tucker on Sep 30, 2009 8:42:32 AM

At this point, even my dad has asked me what I think about Google Wave (sorry Dad for any tech-savvy intimations!). Since Wave is in the process of rolling out to a much larger audience of testers and developers, it seemed like an appropriate time to jot down some thoughts about it. But first, an announcement: as widely discussed around the web, Wave uses the XMPP protocol under the hood and in particular works with the Openfire XMPP server (see Wave Federation install docs). Openfire was developed by Jive and we continue to sponsor it as an Open Source project. Up to this point, Openfire has been available under the GPL license. We've moved Openfire to the more liberal Apache 2.0 Open Source license, which is the same license used for the Google Wave Federation project. This change is already reflected in the Openfire source tree and an official release will be made soon. We hope and believe that the more liberal Apache 2.0 license will help unleash a new wave of innovation around Openfire (bad pun gleefully intended).

 

So, Wave itself -- though the project is still in the early stages (and far from ready for prime-time, especially in an enterprise setting) it's generated an enormous amount of buzz. No doubt a large part of that excitement is due to it being from Google. But more importantly, Wave is pushing the boundaries of what's possible in a web browser with a super rich and real-time user experience. It serves as inspiration to all of us that develop collaboration software. While it's still a bit early for Jive to have an official position on Wave, we're definitely following it closely and the Wave concepts align well with our roadmap. So much has been written about Wave already that I won't attempt to duplicate any of the existing detailed overviews. But I do have my personal three favorite things about Wave:

 

  1. Wave will help drive adoption of HTML 5 by serving as such a compelling example of what that technology makes possible.
  2. Wave uses XMPP as the back-end protocol. Yes, I'm a nerd for loving a protocol.
  3. Federation is baked-in. This was a visionary move by Google and big win for an open internet in the new world of monolithic web sites/services.

 

It will be fun to watch where all of this goes.

4,091 Views Tags: xmpp, planet-jabber, openfire, google_wave


Add a comment Leave a comment on this blog post.
Sep 30, 2009 10:16 AM Matthew Tagg  says:

I think wave + SBS makes perfect sense. Sure its early days, but the possibilities in brings to realtime collaboration seem too good to pass up.

 

Any plans idn the meantime to update SBS content editor? It's the Achilles heel on an otherwise revolutionary piece of software.

(case in point:  Aaargh just as I'm typing this my cursor has disappeared from this input box letting me guess where I type) [FF3.5 Mac Osx 10.6)

Sep 30, 2009 12:14 PM Matt Tucker Matt Tucker    says in response to Matthew Tagg:

Matthew -- based on our Twitter back and forth, it sounds like you'll see a huge amount of improvement by upgrading to the latest Jive SBS release. The RTE is definitely an on-going investment area for us though!

Oct 1, 2009 8:08 AM Marcelo Terres  says:

Openfire looks abandoned.

 

Now that Google will use it, do you think we'll have new features and new versions ?


Regards,

Oct 2, 2009 2:57 PM VT3311 VT3311    says:

Thanks for this post, I've been wondering how Google Wave has been faring and has been genereally received so far. Personally I'm not touching it yet but since the good news keep coming, that might change soon.

Oct 7, 2009 11:39 AM SwzMaster  says:

still wait to see how it wave

Oct 24, 2009 12:05 AM bucabay  says:

Why isn't there an update regarding Google Wave on the Openfire project page? That would seem like the way to re-ignite OpenFire..

Dec 24, 2009 1:54 AM Wilfried  says:

Is it just me, or are we not missing the real big carrot? I'm running a community for 3 years now and THE real competitor for any community software is eMail. Joining email and wiki into a single document is about the biggest business bang that anybody can think of. The reason why email is so popular is because it is easy and rich. The reason why wiki won't grow is WML. Combine those two and be the first to sunset Outlook and Lotus Notes. Replacing wiki with wave inside SBS is the only thing for me that makes sense. BIG sense. Don't try to load a Ferrari on a horsetrailer by embedding wave in a wiki.