<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Thoughts On Scalable XMPP Bots</title>
	<atom:link href="http://metajack.wordpress.com/2008/08/04/thoughts-on-scalable-xmpp-bots/feed/" rel="self" type="application/rss+xml" />
	<link>http://metajack.wordpress.com/2008/08/04/thoughts-on-scalable-xmpp-bots/</link>
	<description>a blog about startups and code</description>
	<lastBuildDate>Thu, 18 Dec 2008 03:41:49 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Labnotes &#187; Rounded Corners 212 -</title>
		<link>http://metajack.wordpress.com/2008/08/04/thoughts-on-scalable-xmpp-bots/#comment-262</link>
		<dc:creator>Labnotes &#187; Rounded Corners 212 -</dc:creator>
		<pubDate>Fri, 08 Aug 2008 07:16:29 +0000</pubDate>
		<guid isPermaLink="false">http://metajack.wordpress.com/?p=77#comment-262</guid>
		<description>[...] Bots. Apparently there is a way to tie message processing to domains without messing with roasters. Exactly what I needed for my little XMPP [...]</description>
		<content:encoded><![CDATA[<p>[...] Bots. Apparently there is a way to tie message processing to domains without messing with roasters. Exactly what I needed for my little XMPP [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: spsneo</title>
		<link>http://metajack.wordpress.com/2008/08/04/thoughts-on-scalable-xmpp-bots/#comment-261</link>
		<dc:creator>spsneo</dc:creator>
		<pubDate>Wed, 06 Aug 2008 21:06:37 +0000</pubDate>
		<guid isPermaLink="false">http://metajack.wordpress.com/?p=77#comment-261</guid>
		<description>I want to host a xmpp bot.
Will I be able to connect xmpp through http proxy ?</description>
		<content:encoded><![CDATA[<p>I want to host a xmpp bot.<br />
Will I be able to connect xmpp through http proxy ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kellan</title>
		<link>http://metajack.wordpress.com/2008/08/04/thoughts-on-scalable-xmpp-bots/#comment-260</link>
		<dc:creator>kellan</dc:creator>
		<pubDate>Wed, 06 Aug 2008 20:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://metajack.wordpress.com/?p=77#comment-260</guid>
		<description>Just to third, confirmed ejabberd round robin load balancing components.  But it *seems* like you could re-use the your presumably more sophisticated (and possibly implemented in hard ware) load balancing infrastructures if you move to s2s.  

Of course, sophistication is just another word for more ways to break down :)</description>
		<content:encoded><![CDATA[<p>Just to third, confirmed ejabberd round robin load balancing components.  But it *seems* like you could re-use the your presumably more sophisticated (and possibly implemented in hard ware) load balancing infrastructures if you move to s2s.  </p>
<p>Of course, sophistication is just another word for more ways to break down <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ezra</title>
		<link>http://metajack.wordpress.com/2008/08/04/thoughts-on-scalable-xmpp-bots/#comment-258</link>
		<dc:creator>ezra</dc:creator>
		<pubDate>Tue, 05 Aug 2008 01:36:37 +0000</pubDate>
		<guid isPermaLink="false">http://metajack.wordpress.com/?p=77#comment-258</guid>
		<description>Yes ejabberd does round robin load balancing of components registered as the same component name.</description>
		<content:encoded><![CDATA[<p>Yes ejabberd does round robin load balancing of components registered as the same component name.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: metajack</title>
		<link>http://metajack.wordpress.com/2008/08/04/thoughts-on-scalable-xmpp-bots/#comment-255</link>
		<dc:creator>metajack</dc:creator>
		<pubDate>Mon, 04 Aug 2008 18:58:12 +0000</pubDate>
		<guid isPermaLink="false">http://metajack.wordpress.com/?p=77#comment-255</guid>
		<description>@anders: So if multiple component connections occur with the same component name, ejabberd will automatically round robin?  If so, that at least solves the load balancing piece for ejabberd.</description>
		<content:encoded><![CDATA[<p>@anders: So if multiple component connections occur with the same component name, ejabberd will automatically round robin?  If so, that at least solves the load balancing piece for ejabberd.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anders conbere</title>
		<link>http://metajack.wordpress.com/2008/08/04/thoughts-on-scalable-xmpp-bots/#comment-254</link>
		<dc:creator>Anders conbere</dc:creator>
		<pubDate>Mon, 04 Aug 2008 18:56:00 +0000</pubDate>
		<guid isPermaLink="false">http://metajack.wordpress.com/?p=77#comment-254</guid>
		<description>My understanding is that at least in Ejabberd the current implementation round-robins components. Providing at least some degree of protection for availability.

~ Anders</description>
		<content:encoded><![CDATA[<p>My understanding is that at least in Ejabberd the current implementation round-robins components. Providing at least some degree of protection for availability.</p>
<p>~ Anders</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Saint-Andre</title>
		<link>http://metajack.wordpress.com/2008/08/04/thoughts-on-scalable-xmpp-bots/#comment-253</link>
		<dc:creator>Peter Saint-Andre</dc:creator>
		<pubDate>Mon, 04 Aug 2008 17:58:18 +0000</pubDate>
		<guid isPermaLink="false">http://metajack.wordpress.com/?p=77#comment-253</guid>
		<description>Hi Jack, that&#039;s a good overview -- thanks for posting!</description>
		<content:encoded><![CDATA[<p>Hi Jack, that&#8217;s a good overview &#8212; thanks for posting!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
