Posts Tagged ‘protocol’

Post

Why Email Needs Replacing (or Why Wave Matters)

In Post on 2010-03-30 by Joshua Tagged: , , ,

wave-email.jpg

It’s Old

Why it’s bad:

Email was invented 40 years ago to deal with a very different set of communication problems. The web didn’t exist, and email was a simple way to get text from one place to another. Think black screens with green writing and geeks talking to geeks across America. Now we have Twitter, Facebook, and whole new ways to communicate, but our basic building block is email. Everything useful eventually finds an implementation in email, but it’s ill-suited for the task. Sure it’s universal, but just sending images was an afterthought!

How Google Wave can help:

It’s built on the latest proven internet technologies. It’s built from the ground up to handle rich media of all different types but still retains some of the things that worked for email in the beginning, like addresses using the @ symbol to send messages to the right place.

Read More »

t

Wave Protocol Installation Instructions

In Link on 2009-07-22 by Joshua Tagged: , ,

Google has released the first prototype Wave Protocol Server, for people to begin the steps to creating their own Wave servers. The code requires a Java enabled server with Openfire XMPP installed. The installation instructions include the details of preparing Openfire for use as a Wave server.

Installation of the Wave Protocol [Google Code]

Post

Wave the Protocol

In Post on 2009-06-08 by Joshua Tagged: ,

The final and most exciting of the “Three Ps” is Wave as a protocol. The Product is Google owned and operated. The Platform enhances their offering. The Protocol opens the code up and makes it available for others to use, re-create, and improve. From the day Google Wave becomes available, the Wave Protocol will allow other parties to create competing products that will interoperate with Google’s offering.

To me, this is the most exciting and wonderful part of Google’s announcement. No one company stands a chance of dethroning email as the reigning form of communication on the ‘net. By opening up their idea, Wave stands a chance of becoming the way we communicate into the next decade. Only by giving users a choice about where their business critical data is stored will users begin to trust Wave like they have learned to trust email.

Google have stated that when they launch Google Wave, anyone will be able to download the “lions share” of the code to run on their own servers promising that the open-source code will run and operate almost exactly the same as the Product they offer on Google’s own servers. They liken it to the SMTP (email sending) protocol — open for everyone to create and use their own implementations as they see fit, and email has taken off because of it.

t

Google Wave was recently announced at the Google I/O developer conference. This is an amazing video and well worth the hour and twenty it will take you to watch it. If you’d like to know what the future of web communication might look like, you can get a head start right here.

Wave Preview at the Google I/O Developer Conferencee

Tagged: , , , on 2009-06-04 by Joshua

View Comments