<?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"
	>
<channel>
	<title>Comments on: Distributed programming with Jabber and EventMachine</title>
	<atom:link href="http://nutrun.com/weblog/distributed-programming-with-jabber-and-eventmachine/feed/" rel="self" type="application/rss+xml" />
	<link>http://nutrun.com/weblog/distributed-programming-with-jabber-and-eventmachine/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Sat, 05 Jul 2008 16:41:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Dan</title>
		<link>http://nutrun.com/weblog/distributed-programming-with-jabber-and-eventmachine/#comment-1106</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Wed, 02 Jul 2008 17:41:33 +0000</pubDate>
		<guid isPermaLink="false">http://nutrun.com/?p=137#comment-1106</guid>
		<description>I haven't used the Jabber protocol as a message queue before like this, but my only concern is does it allow some sort of way to ensure that each message has guaranteed one-time delivery?  If I sent out a message to the "cloud" I would want to make sure every message is either processed by a worker or held in the queue until a worker is available.  My concern is that if workers were backed up, or (worst case) completely down, I would want to ensure no messages were lost.</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t used the Jabber protocol as a message queue before like this, but my only concern is does it allow some sort of way to ensure that each message has guaranteed one-time delivery?  If I sent out a message to the &#8220;cloud&#8221; I would want to make sure every message is either processed by a worker or held in the queue until a worker is available.  My concern is that if workers were backed up, or (worst case) completely down, I would want to ensure no messages were lost.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Allam</title>
		<link>http://nutrun.com/weblog/distributed-programming-with-jabber-and-eventmachine/#comment-917</link>
		<dc:creator>Eric Allam</dc:creator>
		<pubDate>Fri, 23 May 2008 16:19:13 +0000</pubDate>
		<guid isPermaLink="false">http://nutrun.com/?p=137#comment-917</guid>
		<description>I like the idea, and I think this could be a good fit for the Jabber PubSub spec (http://www.xmpp.org/extensions/xep-0060.html).  This way multiple application could "subscribe" to a node where other applications can pass events, and those applications can process those events however they need to.  This event model could be easily distributed, and if you used ejabberd as your jabber server, you could have a pretty powerful and fault tolerant way to perform distributed programming tasks.  Very very interesting.</description>
		<content:encoded><![CDATA[<p>I like the idea, and I think this could be a good fit for the Jabber PubSub spec (http://www.xmpp.org/extensions/xep-0060.html).  This way multiple application could &#8220;subscribe&#8221; to a node where other applications can pass events, and those applications can process those events however they need to.  This event model could be easily distributed, and if you used ejabberd as your jabber server, you could have a pretty powerful and fault tolerant way to perform distributed programming tasks.  Very very interesting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: An EventMachine Tutorial &#124; 20bits</title>
		<link>http://nutrun.com/weblog/distributed-programming-with-jabber-and-eventmachine/#comment-902</link>
		<dc:creator>An EventMachine Tutorial &#124; 20bits</dc:creator>
		<pubDate>Thu, 22 May 2008 02:18:51 +0000</pubDate>
		<guid isPermaLink="false">http://nutrun.com/?p=137#comment-902</guid>
		<description>[...] also an article about using EventMachine with Jabber to create a Jabber Bot that's worth [...]</description>
		<content:encoded><![CDATA[<p>[...] also an article about using EventMachine with Jabber to create a Jabber Bot that&#8217;s worth [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nome do Jogo &#187; Artigo &#187; Rails Podcast Brasil - Epis</title>
		<link>http://nutrun.com/weblog/distributed-programming-with-jabber-and-eventmachine/#comment-746</link>
		<dc:creator>Nome do Jogo &#187; Artigo &#187; Rails Podcast Brasil - Epis</dc:creator>
		<pubDate>Fri, 09 May 2008 16:15:40 +0000</pubDate>
		<guid isPermaLink="false">http://nutrun.com/?p=137#comment-746</guid>
		<description>[...] Distributed programming with Jabber and EventMachine [...]</description>
		<content:encoded><![CDATA[<p>[...] Distributed programming with Jabber and EventMachine [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2008-05-07 at Topper&#8217;s Blog</title>
		<link>http://nutrun.com/weblog/distributed-programming-with-jabber-and-eventmachine/#comment-697</link>
		<dc:creator>links for 2008-05-07 at Topper&#8217;s Blog</dc:creator>
		<pubDate>Wed, 07 May 2008 04:32:46 +0000</pubDate>
		<guid isPermaLink="false">http://nutrun.com/?p=137#comment-697</guid>
		<description>[...] nutrun » Blog Archive » Distributed programming with Jabber and EventMachine (tags: jabber eventmachine delayed processing method rails) [...]</description>
		<content:encoded><![CDATA[<p>[...] nutrun » Blog Archive » Distributed programming with Jabber and EventMachine (tags: jabber eventmachine delayed processing method rails) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Punch Barrel / Distributed programming with Jabber and EventMachine</title>
		<link>http://nutrun.com/weblog/distributed-programming-with-jabber-and-eventmachine/#comment-687</link>
		<dc:creator>The Punch Barrel / Distributed programming with Jabber and EventMachine</dc:creator>
		<pubDate>Tue, 06 May 2008 19:45:28 +0000</pubDate>
		<guid isPermaLink="false">http://nutrun.com/?p=137#comment-687</guid>
		<description>[...] nutrun » Blog Archive » Distributed programming with Jabber and EventMachine [...]</description>
		<content:encoded><![CDATA[<p>[...] nutrun » Blog Archive » Distributed programming with Jabber and EventMachine [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web 2.0 Announcer</title>
		<link>http://nutrun.com/weblog/distributed-programming-with-jabber-and-eventmachine/#comment-680</link>
		<dc:creator>Web 2.0 Announcer</dc:creator>
		<pubDate>Tue, 06 May 2008 09:29:57 +0000</pubDate>
		<guid isPermaLink="false">http://nutrun.com/?p=137#comment-680</guid>
		<description>&lt;strong&gt;nutrun » Blog Archive » Distributed programming with Jabber and EventMachine...&lt;/strong&gt;

[...][...]...</description>
		<content:encoded><![CDATA[<p><strong>nutrun » Blog Archive » Distributed programming with Jabber and EventMachine&#8230;</strong></p>
<p>[...][...]&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web 2.0 Announcer</title>
		<link>http://nutrun.com/weblog/distributed-programming-with-jabber-and-eventmachine/#comment-679</link>
		<dc:creator>Web 2.0 Announcer</dc:creator>
		<pubDate>Tue, 06 May 2008 09:19:06 +0000</pubDate>
		<guid isPermaLink="false">http://nutrun.com/?p=137#comment-679</guid>
		<description>&lt;strong&gt;Distributed programming with Jabber and EventMachine...&lt;/strong&gt;

[...]Jabber and its underlying protocol XMPP are typically associated with instant messaging applications, although the breadth and flexibility of the technology allows for implementations that can span further from traditional online chatting.[...]...</description>
		<content:encoded><![CDATA[<p><strong>Distributed programming with Jabber and EventMachine&#8230;</strong></p>
<p>[...]Jabber and its underlying protocol XMPP are typically associated with instant messaging applications, although the breadth and flexibility of the technology allows for implementations that can span further from traditional online chatting.[...]&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2008-05-06 &#124; Libin Pan</title>
		<link>http://nutrun.com/weblog/distributed-programming-with-jabber-and-eventmachine/#comment-674</link>
		<dc:creator>links for 2008-05-06 &#124; Libin Pan</dc:creator>
		<pubDate>Tue, 06 May 2008 06:34:52 +0000</pubDate>
		<guid isPermaLink="false">http://nutrun.com/?p=137#comment-674</guid>
		<description>[...] nutrun » Blog Archive » Distributed programming with Jabber and EventMachine Distributed programming with Jabber and EventMachine (tags: development distributed events jabber ruby xmpp) [...]</description>
		<content:encoded><![CDATA[<p>[...] nutrun » Blog Archive » Distributed programming with Jabber and EventMachine Distributed programming with Jabber and EventMachine (tags: development distributed events jabber ruby xmpp) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://nutrun.com/weblog/distributed-programming-with-jabber-and-eventmachine/#comment-664</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Tue, 06 May 2008 01:25:55 +0000</pubDate>
		<guid isPermaLink="false">http://nutrun.com/?p=137#comment-664</guid>
		<description>I do hope XMPP doesn't become the event system of distributed storage.  I wrote an instant messenger on it once and the protocol is just plain bad.  Lots of elements called 'a' and 'x' all with different namespaces.  
It's about time we had a new IM protocol, maybe based around ATOM.</description>
		<content:encoded><![CDATA[<p>I do hope XMPP doesn&#8217;t become the event system of distributed storage.  I wrote an instant messenger on it once and the protocol is just plain bad.  Lots of elements called &#8216;a&#8217; and &#8216;x&#8217; all with different namespaces.<br />
It&#8217;s about time we had a new IM protocol, maybe based around ATOM.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
