<?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: Merb: render_deferred and render_then_call</title>
	<atom:link href="http://nutrun.com/weblog/merb-render_deferred-and-render_then_call/feed/" rel="self" type="application/rss+xml" />
	<link>http://nutrun.com/weblog/merb-render_deferred-and-render_then_call/</link>
	<description>nutrun</description>
	<pubDate>Sat, 06 Sep 2008 04:22:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: David</title>
		<link>http://nutrun.com/weblog/merb-render_deferred-and-render_then_call/#comment-889</link>
		<dc:creator>David</dc:creator>
		<pubDate>Tue, 20 May 2008 19:23:36 +0000</pubDate>
		<guid isPermaLink="false">http://nutrun.com/?p=133#comment-889</guid>
		<description>This is amazing! Thank you!

content-type seems to be hard coded to 'text/html'
I'm having a hard time getting something else.</description>
		<content:encoded><![CDATA[<p>This is amazing! Thank you!</p>
<p>content-type seems to be hard coded to &#8216;text/html&#8217;<br />
I&#8217;m having a hard time getting something else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Malamidis</title>
		<link>http://nutrun.com/weblog/merb-render_deferred-and-render_then_call/#comment-443</link>
		<dc:creator>George Malamidis</dc:creator>
		<pubDate>Tue, 22 Apr 2008 23:09:04 +0000</pubDate>
		<guid isPermaLink="false">http://nutrun.com/?p=133#comment-443</guid>
		<description>I assume a lock is used by default to accommodate non thread safe code running behind merb. Not being a huge fan of defensive programming myself, I would have opted for the non-locking option as the default choice, but still, having the option seems like a step forward. 

Sinatra (http://sinatrarb.com), by the way, dispatches without a lock by default, but offers the option to "run safely" if desired.</description>
		<content:encoded><![CDATA[<p>I assume a lock is used by default to accommodate non thread safe code running behind merb. Not being a huge fan of defensive programming myself, I would have opted for the non-locking option as the default choice, but still, having the option seems like a step forward. </p>
<p>Sinatra (http://sinatrarb.com), by the way, dispatches without a lock by default, but offers the option to &#8220;run safely&#8221; if desired.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyle Drake</title>
		<link>http://nutrun.com/weblog/merb-render_deferred-and-render_then_call/#comment-420</link>
		<dc:creator>Kyle Drake</dc:creator>
		<pubDate>Sun, 20 Apr 2008 17:19:48 +0000</pubDate>
		<guid isPermaLink="false">http://nutrun.com/?p=133#comment-420</guid>
		<description>I don't quite understand the ramifications of using these, the Merb docs don't say much about them. Is there any specific cons to using these, besides just the error handling? Why can't I just wrap every single action in my system with a render_deferred? Why doesn't Merb do this by default? I'm sure there's a good reason, I just haven't discovered it yet.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t quite understand the ramifications of using these, the Merb docs don&#8217;t say much about them. Is there any specific cons to using these, besides just the error handling? Why can&#8217;t I just wrap every single action in my system with a render_deferred? Why doesn&#8217;t Merb do this by default? I&#8217;m sure there&#8217;s a good reason, I just haven&#8217;t discovered it yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Hoover</title>
		<link>http://nutrun.com/weblog/merb-render_deferred-and-render_then_call/#comment-409</link>
		<dc:creator>Dave Hoover</dc:creator>
		<pubDate>Fri, 18 Apr 2008 04:34:01 +0000</pubDate>
		<guid isPermaLink="false">http://nutrun.com/?p=133#comment-409</guid>
		<description>Thanks again for this one, George.  I love the flexibility these features provide.</description>
		<content:encoded><![CDATA[<p>Thanks again for this one, George.  I love the flexibility these features provide.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
