<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>bearlog - Latest Comments in Random thoughts about including Google Wave in your data flow</title><link>http://bearlog.disqus.com/</link><description></description><atom:link href="https://bearlog.disqus.com/random_thoughts_about_including_google_wave_in_your_data_flow/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 02 Oct 2009 14:55:03 -0000</lastBuildDate><item><title>Re: Random thoughts about including Google Wave in your data flow</title><link>http://code-bear.com/bearlog/2009/10/02/random-thoughts-about-including-google-wave-in-your-data-flow/#comment-18306117</link><description>&lt;p&gt;Very interactive indeed.  And that'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'm more worried about when a bot is present in 50 wave documents and it's getting 2/3 updates per document and *some* of them need to be distributed to something other than the source doc.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bear</dc:creator><pubDate>Fri, 02 Oct 2009 14:55:03 -0000</pubDate></item><item><title>Re: Random thoughts about including Google Wave in your data flow</title><link>http://code-bear.com/bearlog/2009/10/02/random-thoughts-about-including-google-wave-in-your-data-flow/#comment-18305190</link><description>&lt;p&gt;That Python/Ruby/Perl #Wave bot is pretty interactive!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Reid</dc:creator><pubDate>Fri, 02 Oct 2009 14:34:32 -0000</pubDate></item></channel></rss>