<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Random thoughts about including Google Wave in your data flow</title>
	<atom:link href="http://code-bear.com/bearlog/2009/10/02/random-thoughts-about-including-google-wave-in-your-data-flow/feed/" rel="self" type="application/rss+xml" />
	<link>http://code-bear.com/bearlog/2009/10/02/random-thoughts-about-including-google-wave-in-your-data-flow/</link>
	<description>Gravity is the root of lightness; stillness, the ruler of movement</description>
	<lastBuildDate>Mon, 23 Aug 2010 01:14:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com" />
	<atom:link rel="hub" href="http://superfeedr.com/hubbub" />
		<item>
		<title>By: bear</title>
		<link>http://code-bear.com/bearlog/2009/10/02/random-thoughts-about-including-google-wave-in-your-data-flow/comment-page-1/#comment-144</link>
		<dc:creator>bear</dc:creator>
		<pubDate>Fri, 02 Oct 2009 23:55:03 +0000</pubDate>
		<guid isPermaLink="false">http://code-bear.com/bearlog/2009/10/02/random-thoughts-about-including-google-wave-in-your-data-flow/#comment-144</guid>
		<description>Very interactive indeed.  And that&#039;s a great example of how a bot/extension can be both a sink and a source, that bot probably treats all incoming change requests as discrete/atomic updates - i&#039;m more worried about when a bot is present in 50 wave documents and it&#039;s getting 2/3 updates per document and *some* of them need to be distributed to something other than the source doc.</description>
		<content:encoded><![CDATA[<p>Very interactive indeed.  And that&#39;s a great example of how a bot/extension can be both a sink and a source, that bot probably treats all incoming change requests as discrete/atomic updates &#8211; i&#39;m more worried about when a bot is present in 50 wave documents and it&#39;s getting 2/3 updates per document and *some* of them need to be distributed to something other than the source doc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reid</title>
		<link>http://code-bear.com/bearlog/2009/10/02/random-thoughts-about-including-google-wave-in-your-data-flow/comment-page-1/#comment-143</link>
		<dc:creator>Reid</dc:creator>
		<pubDate>Fri, 02 Oct 2009 23:34:32 +0000</pubDate>
		<guid isPermaLink="false">http://code-bear.com/bearlog/2009/10/02/random-thoughts-about-including-google-wave-in-your-data-flow/#comment-143</guid>
		<description>That Python/Ruby/Perl #Wave bot is pretty interactive!</description>
		<content:encoded><![CDATA[<p>That Python/Ruby/Perl #Wave bot is pretty interactive!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bear</title>
		<link>http://code-bear.com/bearlog/2009/10/02/random-thoughts-about-including-google-wave-in-your-data-flow/comment-page-1/#comment-70</link>
		<dc:creator>bear</dc:creator>
		<pubDate>Fri, 02 Oct 2009 19:55:03 +0000</pubDate>
		<guid isPermaLink="false">http://code-bear.com/bearlog/2009/10/02/random-thoughts-about-including-google-wave-in-your-data-flow/#comment-70</guid>
		<description>Very interactive indeed.  And that&#039;s a great example of how a bot/extension can be both a sink and a source, that bot probably treats all incoming change requests as discrete/atomic updates - i&#039;m more worried about when a bot is present in 50 wave documents and it&#039;s getting 2/3 updates per document and *some* of them need to be distributed to something other than the source doc.</description>
		<content:encoded><![CDATA[<p>Very interactive indeed.  And that&#39;s a great example of how a bot/extension can be both a sink and a source, that bot probably treats all incoming change requests as discrete/atomic updates &#8211; i&#39;m more worried about when a bot is present in 50 wave documents and it&#39;s getting 2/3 updates per document and *some* of them need to be distributed to something other than the source doc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reid</title>
		<link>http://code-bear.com/bearlog/2009/10/02/random-thoughts-about-including-google-wave-in-your-data-flow/comment-page-1/#comment-69</link>
		<dc:creator>Reid</dc:creator>
		<pubDate>Fri, 02 Oct 2009 19:34:32 +0000</pubDate>
		<guid isPermaLink="false">http://code-bear.com/bearlog/2009/10/02/random-thoughts-about-including-google-wave-in-your-data-flow/#comment-69</guid>
		<description>That Python/Ruby/Perl #Wave bot is pretty interactive!</description>
		<content:encoded><![CDATA[<p>That Python/Ruby/Perl #Wave bot is pretty interactive!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
