<?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: I </title>
	<atom:link href="http://nachbaur.com/blog/i-3-httpengine/feed" rel="self" type="application/rss+xml" />
	<link>http://nachbaur.com/blog/i-3-httpengine</link>
	<description>Making broken software somewhat less broken</description>
	<lastBuildDate>Thu, 19 Aug 2010 15:38:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Mike Nachbaur</title>
		<link>http://nachbaur.com/blog/i-3-httpengine/comment-page-1#comment-56</link>
		<dc:creator>Mike Nachbaur</dc:creator>
		<pubDate>Tue, 26 May 2009 21:28:19 +0000</pubDate>
		<guid isPermaLink="false">http://nachbaur.com/?p=27#comment-56</guid>
		<description>Yeah, I&#039;ve looked at Mojo, but for what we&#039;re doing it&#039;s still a bit heavyweight.  Thanks to &lt;a HREF=&quot;http://blog.robin.smidsrod.no/index.php/2009/05/26/memory-footprint-of-popular-cpan-modules&quot; REL=&quot;nofollow&quot;&gt;this article on the memory footprint of CPAN modules&lt;/a&gt;, I discovered CGI::Simple which should do enough of what we need to allow this project to move forward.&lt;br /&gt;&lt;br /&gt;This is a really simple webapp though; in the future our more complicated administrative interface will need to move to FastCGI away from mod_perl2, so we&#039;ll look at Mojo or HTTP::Engine again then.</description>
		<content:encoded><![CDATA[<p>Yeah, I&#8217;ve looked at Mojo, but for what we&#8217;re doing it&#8217;s still a bit heavyweight.  Thanks to <a HREF="http://blog.robin.smidsrod.no/index.php/2009/05/26/memory-footprint-of-popular-cpan-modules" REL="nofollow">this article on the memory footprint of CPAN modules</a>, I discovered CGI::Simple which should do enough of what we need to allow this project to move forward.</p>
<p>This is a really simple webapp though; in the future our more complicated administrative interface will need to move to FastCGI away from mod_perl2, so we&#8217;ll look at Mojo or HTTP::Engine again then.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: melo</title>
		<link>http://nachbaur.com/blog/i-3-httpengine/comment-page-1#comment-55</link>
		<dc:creator>melo</dc:creator>
		<pubDate>Sat, 23 May 2009 06:37:34 +0000</pubDate>
		<guid isPermaLink="false">http://nachbaur.com/?p=27#comment-55</guid>
		<description>Before you start writting your own HTTP::Engine::Simple, take a look at Mojo (I recommend that you use the git version, a new release is imminent and it is much niceier).&lt;br /&gt;&lt;br /&gt;Not only it has zero dependencies (which seems something that you need), it also is the most HTTP spec compliant stack on CPAN.&lt;br /&gt;&lt;br /&gt;Even better: it includes a full MVC Web framework with modern dispatching.&lt;br /&gt;&lt;br /&gt;I use it at $work.</description>
		<content:encoded><![CDATA[<p>Before you start writting your own HTTP::Engine::Simple, take a look at Mojo (I recommend that you use the git version, a new release is imminent and it is much niceier).</p>
<p>Not only it has zero dependencies (which seems something that you need), it also is the most HTTP spec compliant stack on CPAN.</p>
<p>Even better: it includes a full MVC Web framework with modern dispatching.</p>
<p>I use it at $work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
