<?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: Multi threaded Ruby on Rails actions?</title>
	<atom:link href="http://www.mrblack.co.uk/blog/2007/03/22/multi-threaded-ruby-on-rails-actions/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mrblack.co.uk/blog/2007/03/22/multi-threaded-ruby-on-rails-actions/</link>
	<description></description>
	<pubDate>Wed, 07 Jan 2009 01:53:43 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Chuck Vose</title>
		<link>http://www.mrblack.co.uk/blog/2007/03/22/multi-threaded-ruby-on-rails-actions/#comment-43397</link>
		<dc:creator>Chuck Vose</dc:creator>
		<pubDate>Fri, 16 Nov 2007 14:01:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.mrblack.co.uk/blog/2007/03/22/multi-threaded-ruby-on-rails-actions/#comment-43397</guid>
		<description>If you haven't already found the answer to this -- which I doubt; you being an enterprising rails developer -- have you considered running BackgrounDRb? Building your own threading would be fine, you can use Ruby's Thread class, but it might have a lot of unintended consequences if you don't have a very strong background in multithreaded apps.

The other option would be to have a observer that watches for changes and automatically builds pdfs for what it needs to. Could even run these observers in BackgrounDRb for extra points. :P</description>
		<content:encoded><![CDATA[<p>If you haven&#8217;t already found the answer to this &#8212; which I doubt; you being an enterprising rails developer &#8212; have you considered running BackgrounDRb? Building your own threading would be fine, you can use Ruby&#8217;s Thread class, but it might have a lot of unintended consequences if you don&#8217;t have a very strong background in multithreaded apps.</p>
<p>The other option would be to have a observer that watches for changes and automatically builds pdfs for what it needs to. Could even run these observers in BackgrounDRb for extra points. :P</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: site admin</title>
		<link>http://www.mrblack.co.uk/blog/2007/03/22/multi-threaded-ruby-on-rails-actions/#comment-7337</link>
		<dc:creator>site admin</dc:creator>
		<pubDate>Fri, 23 Mar 2007 09:33:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.mrblack.co.uk/blog/2007/03/22/multi-threaded-ruby-on-rails-actions/#comment-7337</guid>
		<description>Humm interesting.  Thanks!</description>
		<content:encoded><![CDATA[<p>Humm interesting.  Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dysinger</title>
		<link>http://www.mrblack.co.uk/blog/2007/03/22/multi-threaded-ruby-on-rails-actions/#comment-7317</link>
		<dc:creator>Dysinger</dc:creator>
		<pubDate>Fri, 23 Mar 2007 01:17:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.mrblack.co.uk/blog/2007/03/22/multi-threaded-ruby-on-rails-actions/#comment-7317</guid>
		<description>Use a message queue and topic to queue and broadcast your requests around to a cluster of PDF report servers in the background.

http://rubyforge.org/projects/reliable-msg/</description>
		<content:encoded><![CDATA[<p>Use a message queue and topic to queue and broadcast your requests around to a cluster of PDF report servers in the background.</p>
<p><a href="http://rubyforge.org/projects/reliable-msg/" rel="nofollow">http://rubyforge.org/projects/reliable-msg/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
