So here's the deal with Wave: If you deal in technology, and you get this one wrong, you'll miss the boat. And it's a big boat. If, on the other hand, you get this one right, you have the potential to do some incredible innovation.
In a nutshell, this is the next revolutionary leap in Internet application architecture. Maybe the first truly revolutionary leap since HTTP itself.
I've been wanting to write this post for a while, but first I wanted to read fully thru and digest the specs and available code. I haven't done any posts about XMPP for quite a while, but you're going to start hearing a whole lot about it, and not just from me.
What is it?
Ok so what exactly Google Wave is can be confusing, because there are three parts: the protocol, the server, and the client. A lot of people are really going to miss the boat here if they don't keep the distinction between the three in mind, because I see a lot of people focusing on the wrong parts.
The Protocol
At its core, Wave is an extension to the XMPP protocol. This is the REALLY important part