<?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: New in Rails: ActiveResource timeouts and why it matters</title>
	<atom:link href="http://blog.codefront.net/2008/04/22/new-in-rails-activeresource-timeouts-and-why-it-matters/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.codefront.net/2008/04/22/new-in-rails-activeresource-timeouts-and-why-it-matters/</link>
	<description>Rails, Firefox, Anime, Mac</description>
	<lastBuildDate>Fri, 05 Mar 2010 23:29:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: &#187; Nginx &#8220;24: Too many open files&#8221; error with Rails? Here&#8217;s why. :: Relentless Simplicity :: The Bonanzle Tech Blog</title>
		<link>http://blog.codefront.net/2008/04/22/new-in-rails-activeresource-timeouts-and-why-it-matters/comment-page-1/#comment-694630</link>
		<dc:creator>&#187; Nginx &#8220;24: Too many open files&#8221; error with Rails? Here&#8217;s why. :: Relentless Simplicity :: The Bonanzle Tech Blog</dc:creator>
		<pubDate>Fri, 06 Feb 2009 21:31:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.codefront.net/?p=1100#comment-694630</guid>
		<description>[...] been slow to actually act on:  making remote API calls without timeouts is asking for trouble.   Here is a fine article if you&#8217;re interested in solving that problem in your own site before it is your [...]</description>
		<content:encoded><![CDATA[<p>[...] been slow to actually act on:  making remote API calls without timeouts is asking for trouble.   Here is a fine article if you&#8217;re interested in solving that problem in your own site before it is your [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Le Vosgien du Net &#183; Rails 2.1, ça roule maintenant ! - Le tutoriel complet - 2ème partie</title>
		<link>http://blog.codefront.net/2008/04/22/new-in-rails-activeresource-timeouts-and-why-it-matters/comment-page-1/#comment-660915</link>
		<dc:creator>Le Vosgien du Net &#183; Rails 2.1, ça roule maintenant ! - Le tutoriel complet - 2ème partie</dc:creator>
		<pubDate>Mon, 04 Aug 2008 07:57:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.codefront.net/?p=1100#comment-660915</guid>
		<description>[...] essayez de trouver le plus petit timeout possible pour votre application. Plus d&#8217;informations ici et, bien sûr, nous vous recommandons de faire le moins d&#8217;appels distants possible dans un [...]</description>
		<content:encoded><![CDATA[<p>[...] essayez de trouver le plus petit timeout possible pour votre application. Plus d&#8217;informations ici et, bien sûr, nous vous recommandons de faire le moins d&#8217;appels distants possible dans un [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nome do Jogo &#187; Artigo &#187; Rails Podcast Brasil - Epis?dio 14</title>
		<link>http://blog.codefront.net/2008/04/22/new-in-rails-activeresource-timeouts-and-why-it-matters/comment-page-1/#comment-592316</link>
		<dc:creator>Nome do Jogo &#187; Artigo &#187; Rails Podcast Brasil - Epis?dio 14</dc:creator>
		<pubDate>Fri, 25 Apr 2008 13:00:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.codefront.net/?p=1100#comment-592316</guid>
		<description>[...] New in Rails: ActiveResource timeouts and why it matters [...]</description>
		<content:encoded><![CDATA[<p>[...] New in Rails: ActiveResource timeouts and why it matters [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A Fresh Cup &#187; Blog Archive &#187; Double Shot #193</title>
		<link>http://blog.codefront.net/2008/04/22/new-in-rails-activeresource-timeouts-and-why-it-matters/comment-page-1/#comment-589311</link>
		<dc:creator>A Fresh Cup &#187; Blog Archive &#187; Double Shot #193</dc:creator>
		<pubDate>Wed, 23 Apr 2008 11:31:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.codefront.net/?p=1100#comment-589311</guid>
		<description>[...] New in Rails: ActiveResource Timeouts and why it matters - Protect yourself from the vagaries of other peoples&#8217; servers. [...]</description>
		<content:encoded><![CDATA[<p>[...] New in Rails: ActiveResource Timeouts and why it matters &#8211; Protect yourself from the vagaries of other peoples&#8217; servers. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chu Yeow</title>
		<link>http://blog.codefront.net/2008/04/22/new-in-rails-activeresource-timeouts-and-why-it-matters/comment-page-1/#comment-588559</link>
		<dc:creator>Chu Yeow</dc:creator>
		<pubDate>Wed, 23 Apr 2008 02:05:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.codefront.net/?p=1100#comment-588559</guid>
		<description>Check out http://headius.blogspot.com/2008/02/rubys-threadraise-threadkill-timeoutrb.html. The time out is being applied &lt;em&gt;anyway&lt;/em&gt; (with the default of 60 seconds) whether you specify a timeout or not. So specifying a timeout won&#039;t hurt. But using the &lt;code&gt;timeout&lt;/code&gt; method explicitly sure will!</description>
		<content:encoded><![CDATA[<p>Check out <a href="http://headius.blogspot.com/2008/02/rubys-threadraise-threadkill-timeoutrb.html" rel="nofollow">http://headius.blogspot.com/2008/02/rubys-threadraise-threadkill-timeoutrb.html</a>. The time out is being applied <em>anyway</em> (with the default of 60 seconds) whether you specify a timeout or not. So specifying a timeout won&#8217;t hurt. But using the <code>timeout</code> method explicitly sure will!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Judge</title>
		<link>http://blog.codefront.net/2008/04/22/new-in-rails-activeresource-timeouts-and-why-it-matters/comment-page-1/#comment-587916</link>
		<dc:creator>Mike Judge</dc:creator>
		<pubDate>Tue, 22 Apr 2008 17:32:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.codefront.net/?p=1100#comment-587916</guid>
		<description>We were having lots of memory leaks and traced it back to the Timeout library.  Be aware that it uses threads and when the timeout fires, may leave your system in an inconsistent state.</description>
		<content:encoded><![CDATA[<p>We were having lots of memory leaks and traced it back to the Timeout library.  Be aware that it uses threads and when the timeout fires, may leave your system in an inconsistent state.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
