Personally I think SMTP is the wrong protocol for Wave. I know that Chris argues that it is essential for enterprise, I actually disagree.The wave/email analogy was always a false one. Currently there is no mature wave services. I know that frustrates some people, but frankly it has little to do with lack of email integration. Once it is stable there will be little reason to make it analogous to email.
There is a big difference between integrating wave technology in any client be it email or whatever and merging the two technologies, which I think will be a red headed step child.It is kind of like trying to make phone and email analogous, sure there are ways of bridging the gap but they are clearly not the same. You can help streamline forms of communication, like facebook is doing. That gives you a step gap. If wave itself isn't useful to enterprise, no attempts at making it like email is going to make it more useful than email. The primary aim of WAIB is to be easy to set up and useful. Google was slow to open up Wave to open up wave to the open source community. Some people were pissed off by that more than others, and people got different ideas. It is actually quite a tough nut to crack. You can't rush the early stages. ----- Original Message ---- From: Chris Harvey <[email protected]> To: [email protected] Sent: Tue, 22 February, 2011 9:12:35 Subject: Re: Question about Wave-Dev | Does a more elaborated attempt for email integration with wave exist? Yes. The iotaWave project is predicated on the notion that wave and eMail *must* be tightly integrated for wave to make a significant impact on the enterprise market. -- Chris the wave practice <http://thewavepractice.com> iotawave.org Singapore
