<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: What would email look like if it was invented today?</title>
	<atom:link href="http://paulmcewan.com/index.php/2009/05/28/google-wave-the-future-of-email/feed/" rel="self" type="application/rss+xml" />
	<link>http://paulmcewan.com/index.php/2009/05/28/google-wave-the-future-of-email/</link>
	<description>A street level view with curb appeal</description>
	<lastBuildDate>Mon, 21 Mar 2011 20:24:22 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: admin</title>
		<link>http://paulmcewan.com/index.php/2009/05/28/google-wave-the-future-of-email/comment-page-1/#comment-579</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 29 May 2009 23:31:12 +0000</pubDate>
		<guid isPermaLink="false">http://paulmcewan.com/?p=251#comment-579</guid>
		<description>Hi Bill, I am glad you went. I have heard the presentation was impressive. Thanks for describing the 3 &quot;P&quot;s here. It makes a lot of sense now when many forecast it to be a success.</description>
		<content:encoded><![CDATA[<p>Hi Bill, I am glad you went. I have heard the presentation was impressive. Thanks for describing the 3 &#8220;P&#8221;s here. It makes a lot of sense now when many forecast it to be a success.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Skrypnyk</title>
		<link>http://paulmcewan.com/index.php/2009/05/28/google-wave-the-future-of-email/comment-page-1/#comment-578</link>
		<dc:creator>Bill Skrypnyk</dc:creator>
		<pubDate>Fri, 29 May 2009 19:19:34 +0000</pubDate>
		<guid isPermaLink="false">http://paulmcewan.com/?p=251#comment-578</guid>
		<description>Paul, I was lucky enough to be in the cheering crowd! The impact of the announcement was indeed staggering. I plan to post a few thoughts of my own on the subject, but briefly, I think it&#039;s important to remember the 3 &quot;P&quot;s of the Wave, as they were presented at the Google I/O: Product, Platform and Protocol.

- Product: very impressive HTML5 driven client in the browser: real time data push, fully built on GWT (doesn&#039;t run in IE, althought IE7 is close to working). 

- Platform: even more impressive! Wave will have open APIs! The demonstration included snippets where a wave &quot;gadget&quot; was included on a 3rd party website and was interacting in real time with the &quot;dashboard&quot;. Another demo showed a bug report being created directly from the wave client in a bug reporting system

- Protocol: most obscure but probably *THE* most impressive. There will be no single central location where wave is &quot;hosted&quot;. It&#039;s not going to be Google, or any other major vendor. Just like modern mail servers, it will be possible to host &quot;wave servers&quot; locally to a business. In fact, it will probably be very much like running a mail server: it&#039;s the open federation that will make the things tick.

It&#039;s hard to underestimate this. If (and only if) this take off and indeed gets traction and adoption; this could lead to a paradigm shift in the way that communication happens on the internet. Such forms of communication as email, instant messaging, micro-blogging, blogging, forums, newsgroups, etc may all blend into one: waves. (If wave takes off, which I very much hope it will.) I am sure it won&#039;t be a trivial task and it will take someone of Google&#039;s magnitude to do it.</description>
		<content:encoded><![CDATA[<p>Paul, I was lucky enough to be in the cheering crowd! The impact of the announcement was indeed staggering. I plan to post a few thoughts of my own on the subject, but briefly, I think it&#8217;s important to remember the 3 &#8220;P&#8221;s of the Wave, as they were presented at the Google I/O: Product, Platform and Protocol.</p>
<p>- Product: very impressive HTML5 driven client in the browser: real time data push, fully built on GWT (doesn&#8217;t run in IE, althought IE7 is close to working). </p>
<p>- Platform: even more impressive! Wave will have open APIs! The demonstration included snippets where a wave &#8220;gadget&#8221; was included on a 3rd party website and was interacting in real time with the &#8220;dashboard&#8221;. Another demo showed a bug report being created directly from the wave client in a bug reporting system</p>
<p>- Protocol: most obscure but probably *THE* most impressive. There will be no single central location where wave is &#8220;hosted&#8221;. It&#8217;s not going to be Google, or any other major vendor. Just like modern mail servers, it will be possible to host &#8220;wave servers&#8221; locally to a business. In fact, it will probably be very much like running a mail server: it&#8217;s the open federation that will make the things tick.</p>
<p>It&#8217;s hard to underestimate this. If (and only if) this take off and indeed gets traction and adoption; this could lead to a paradigm shift in the way that communication happens on the internet. Such forms of communication as email, instant messaging, micro-blogging, blogging, forums, newsgroups, etc may all blend into one: waves. (If wave takes off, which I very much hope it will.) I am sure it won&#8217;t be a trivial task and it will take someone of Google&#8217;s magnitude to do it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

