Skip to main content

Bye bye SMTP - Welcome Wave Protocol

It's very interesting to see that Google has developed a new protocol for e-mail, yes SMTP is just too old and boring, Wave protocol will come soon - at least we already have one provider who will implement this new protocol, I call it as a "reference provider", yes, it's Google Wave :-)

Okay before I begin with this story, one thing we need to know:

"Wave is just a protocol (http://www.waveprotocol.org), a specification, just like SMTP, HTTP, HTML, TCP/IP, OpenID, OAuth, OpenSocial, etc. This means that everyone can implement this protocol to build some new products based on it".

"Google Wave (http://wave.google.com) is an implementation of the Wave protocol". A Google product which supports Wave protocol. I also call Google Wave as a reference implementation and reference provider of the Wave protocol.

If you want to understand the terminology in Wave protocol, please check out this article: Google Wave: A Complete Guide.

OK, with those information in the background we can start our discussion...

The big question for me is whether other e-mail providers like YAHOO!, GMX, Web.de, Lycos, etc. will also support this new Wave protocol. IMO this depends on the acceptance of the reference provider within the consumers. If Google Wave can attract a lot of people, all other e-mail providers will slow but surely become less important and their customers will leave them. Who cares to use that old e-mail, boring stuffs? The advantages of Wave protocol against SMTP are quite clear. And this is the point where they will also have to implement and add the new Wave protocol in their products.

What kind of impacts do we have from Wave protocol alltogether?

1. Technically we don't need to have client applications like e-mail SMTP client applications (Outlook, Thunderbird, etc.) since Wave is being designed for web applications. Maybe there will be some Wave client applications (WaveEagle at Mozilla?) but this is not a must. Yeah, Microsoft Outlook will have to do some diets ;-) Throw all those e-mail stuffs away. Just embed Internet Explorer.

2. We will see some new providers playing and fighting for market share. Yes, the "pie" will be open for everyone, come and join Wave protocol and develop your own Wave product. Yes, we can start from the beginning! Web.de, GMX, YAHOO! will still play a role but it can happen that...
  • Google Wave will get the most customers because their implementation is the first at the market. Marketing people know this as "first mover effect".
  • A newcomer "Swiss Inc." from Switzerland will get a lot of customers because their Wave protocol implementation is the most secure one. Yes, nobody can get access to their servers, also not their own goverment since they have their "Wave secret".
  • "WaveSign" (from V...Sign) offers you a real identity. It means that they will check you offline first, whether you are "the really" Lofi Dewanto before you can get a new Wave account. So everyone gets a Wave from this provider can be sure that the person really exists and the identity is checked.
  • It is possible to have "HotWave" (from M..., you know what I mean) rules the Wave world, because it is directly integrated within their operating system. All those Wavelets are directly integrated in the background screen and their widgets, not bad...
So, to all providers, let's get rumble...

3. How about spammer? Spammer will still find their way to "wave-spam". Please check out http://www.wavespam.net. You can get a wave account easily there, no identity check, nothing and of course you can use it to wave-spam everyone.

4. How are the business model(s) of those OpenWave providers? These won't change a lot. Just take a look those SMTP providers today. How can you earn money with consumer web applications today? Nothing. OK, I give up, ... advertisements, ads, and ads, ... :-)

I personally like the new Wave protocol and it's the time to throw away SMTP, so folks let's get started!

Just my 2 cents, happy Wavy!
Lofi.

BTW. here are some links on Wave protocol and Google Wave in German language:

Comments

Popular posts from this blog

Creating Spring Bean dynamically in the Runtime

In my training someone asked me whether it is possible to create an object (a Spring Bean) dynamically so you can choose which implementation you want to have in the runtime. So at the compile time you don't know what object actually should be created yet. The application should decide what object to be created based on a property file.

1. We create an annotation so we can mark the method which should be able to create the object dynamically:

...
package your.package;
...
@Retention(RetentionPolicy.RUNTIME)
public @interface InjectDynamicObject {
}
...
2. Use the new created annotation in your method which should be able to create the object dynamically:
... @Named("customerBo") public class CustomerBoImpl implements CustomerBo { ...     @Override @InjectDynamicObject public Customer getDynamicCustomer() {         return this.dynamicCustomer; } ...
3. Write an aspect with Pointcut and Advise which change the object returned by the method in the step 2:
... @Named @Aspect public class Dyn…

Enterprise Applications Customization with Microservice

Introduction Today in highly paced enterprise environment you, as the leader of enterprise IT division, need to be fast. Simplicity is the key for the speed. What are the key factors to simplify your IT? Three different areas are very important to take care of: Technology, Organisation and Environment(TOE Framework: http://goo.gl/tQlX5z). Here are some detail points for technology and organisation:

1. Technology: in most enterprises there are already one or more ERP and CRM solutions the so called Enterprise Applications. We need to manage them carefully as they support the business processes. In context of the core compentencies most enterprises customize the enterprise applications to fit their needs. We need to manage the customizations in detail as they represent the core competencies and at the same time the differentiation of our enterprise to other competitors. 2. Organisation: working in a small team with different roles and functions is already proved as the best …

Smart Home Sweet Home with Gigaset Elements?

Introduction
Last week I had a chance to try the Smart Home solution from Gigaset Elements. I read some articles about this product which said how easy to install this product for dummy users. Those articles woke my interest and I began to google products for Smart Home solutions.

In this article (German language) you will find a nice overview about some products for Smart Home, which can be bought in Germany. The Nest product from Google is still not available in Germany. Although it seems that RWE will offer Nest products in Germany in couple of months.

The installation of Gigaset Elements was really easy. The problem I encountered was to add the sirensensor. I had to push hard the button on the siren sensor at the same time with the button on the base, so that they can communicate with each other. After about one hour I managed to install everything properly.

Points to mention
Generally the idea is very nice. Gigaset Elements try to push KISS (Keep it Simple Stupid) principle. Howev…