<?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: Why is &quot;Content-type: text/html&quot; displayed at the top of my CGI pages?</title>
	<atom:link href="http://dustyreagan.com/why-is-content-type-texthtml-displayed-at-the-top-of-my-cgi-pages/feed/" rel="self" type="application/rss+xml" />
	<link>http://dustyreagan.com/why-is-content-type-texthtml-displayed-at-the-top-of-my-cgi-pages/</link>
	<description>On Technology &#38; Entrepreneurship</description>
	<lastBuildDate>Thu, 29 Jul 2010 23:29:01 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Jenda</title>
		<link>http://dustyreagan.com/why-is-content-type-texthtml-displayed-at-the-top-of-my-cgi-pages/comment-page-1/#comment-112</link>
		<dc:creator>Jenda</dc:creator>
		<pubDate>Mon, 02 Jun 2008 18:10:17 +0000</pubDate>
		<guid isPermaLink="false">http://dustyreagan.com/why-is-content-type-texthtml-displayed-at-the-top-of-my-cgi-pages/#comment-112</guid>
		<description>Or search in the script for &quot;Content-type&quot; and add &quot;HTTP/1.0 200 OK\n&quot; just before the Content-type.

Also PerlIs is not two times faster. The execution of the script is just as quick in both, the engine that runs the script is the same. The difference is that with perl.exe the webserver has to create a new process for each and every request. It doesn&#039;t for PerlIs. PerlIs runs inside the IIS process (or the AppPool) and no new processes are created.

So the smaller the scripts, the bigger the difference. In both speed and memory footprint.</description>
		<content:encoded><![CDATA[<p>Or search in the script for &#8220;Content-type&#8221; and add &#8220;HTTP/1.0 200 OK\n&#8221; just before the Content-type.</p>
<p>Also PerlIs is not two times faster. The execution of the script is just as quick in both, the engine that runs the script is the same. The difference is that with perl.exe the webserver has to create a new process for each and every request. It doesn&#8217;t for PerlIs. PerlIs runs inside the IIS process (or the AppPool) and no new processes are created.</p>
<p>So the smaller the scripts, the bigger the difference. In both speed and memory footprint.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
