Speculating on Google Wave: is Google really aiming for Http?

I think it just clicked in my head..

Alot of people, especially the end users, think of Wave as just the Google Wave Client and not the potential of the Wave Protocol.

Some people see what they could do extending the experience by connecting and augmenting data from other sources using robot, extension, etc (extending with Wave API).

Others though, have even gone past that even further. It seems that these people are looking into ways to implement their own Wave according to the spec, but different to how Google implemented it. There wont be bots or extension….there’ll just be a communication platform that uses a protocol that supports real time interaction on top of  federated servers, with all the conflict resolution and other issues resolved!

taken from http://waveprotocol.org/

Just like Netscape changed how we browse the web from command lines to hyperlinking, I sense that there’ll be a leap in how we interact with the web. From semi static to fully immersive experience.

Is Wave protocol could really be the new http? Unfortunately I can’t still answer that question with my limited technical knowledge, and I’m challenging you to read the Wave Protocol spec and tell me what it can/can’t do (my email is ronaldwidha at gmail dot com or wave me at ronaldwidha at googlewave dot com).

If it really is a possibility, shouldn’t we really be looking at creating another web ‘browser’ that offers collaborative experience? Shopping online together, reading WIKIs together (SIDE WIKI perhaps) and even more.