<?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: nginx hits #4 on Netcraft</title>
	<atom:link href="http://michaelshadle.com/2008/12/31/nginx-hits-4-on-netcraft/feed/" rel="self" type="application/rss+xml" />
	<link>http://michaelshadle.com/2008/12/31/nginx-hits-4-on-netcraft/</link>
	<description>&#34;Sometimes I don&#039;t know why I even fucking try&#34;</description>
	<lastBuildDate>Thu, 29 Jul 2010 04:41:46 +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</title>
		<link>http://michaelshadle.com/2008/12/31/nginx-hits-4-on-netcraft/comment-page-1/#comment-10210</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Thu, 01 Jan 2009 04:53:56 +0000</pubDate>
		<guid isPermaLink="false">http://michaelshadle.com/?p=153#comment-10210</guid>
		<description>Me too. Right now it is owned by one person (Igor) and he is the gatekeeper for all changes, which is a) comforting but also b) scary.

I&#039;ve just posted asking about native CGI support and of course I&#039;m looking at trying to get SPNEGO introduced into it, which I believe are the main shortcomings I&#039;ve faced. The only other negative about it is that the location {} block syntax can get confusing and nesting it for certain things is kind of lame. Otherwise, it&#039;s been great :)</description>
		<content:encoded><![CDATA[<p>Me too. Right now it is owned by one person (Igor) and he is the gatekeeper for all changes, which is a) comforting but also b) scary.</p>
<p>I've just posted asking about native CGI support and of course I'm looking at trying to get SPNEGO introduced into it, which I believe are the main shortcomings I've faced. The only other negative about it is that the location {} block syntax can get confusing and nesting it for certain things is kind of lame. Otherwise, it's been great <img src='http://michaelshadle.com/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt G</title>
		<link>http://michaelshadle.com/2008/12/31/nginx-hits-4-on-netcraft/comment-page-1/#comment-10206</link>
		<dc:creator>Matt G</dc:creator>
		<pubDate>Wed, 31 Dec 2008 23:26:01 +0000</pubDate>
		<guid isPermaLink="false">http://michaelshadle.com/?p=153#comment-10206</guid>
		<description>Sweet. Really flying under the radar. I hope it develops a following like Apache in terms of core features w/o becoming the bloat monster that is Apache.</description>
		<content:encoded><![CDATA[<p>Sweet. Really flying under the radar. I hope it develops a following like Apache in terms of core features w/o becoming the bloat monster that is Apache.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
