<?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: Playing with lighttpd</title>
	<atom:link href="http://www.miljan.org/main/2007/09/03/playing-with-lighttpd/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.miljan.org/main/2007/09/03/playing-with-lighttpd/</link>
	<description>Wisdom is the key</description>
	<pubDate>Thu, 28 Aug 2008 23:41:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: almir karic</title>
		<link>http://www.miljan.org/main/2007/09/03/playing-with-lighttpd/#comment-1031</link>
		<dc:creator>almir karic</dc:creator>
		<pubDate>Mon, 28 Jan 2008 14:06:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.miljan.org/main/2007/09/03/playing-with-lighttpd/#comment-1031</guid>
		<description>using apache infront of a lighttpd is from my understanding like useless, you still have apache threads/processes serving the content (and thus consuming ram) they recieved from lighttpd to end user. in my setups i do it other way round, lightweight httpd infront choosing what it wants to serve and proxy-ing everything else to apache.</description>
		<content:encoded><![CDATA[<p>using apache infront of a lighttpd is from my understanding like useless, you still have apache threads/processes serving the content (and thus consuming ram) they recieved from lighttpd to end user. in my setups i do it other way round, lightweight httpd infront choosing what it wants to serve and proxy-ing everything else to apache.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
