<?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: PHP 5.3.0 patch now considered stable</title>
	<atom:link href="http://michaelshadle.com/2009/07/31/php-530-patch-now-considered-stable/feed" rel="self" type="application/rss+xml" />
	<link>http://michaelshadle.com/2009/07/31/php-530-patch-now-considered-stable</link>
	<description>&#34;Lazy people are efficient.&#34; - My boss.</description>
	<lastBuildDate>Mon, 30 Apr 2012 14:27:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: mike</title>
		<link>http://michaelshadle.com/2009/07/31/php-530-patch-now-considered-stable/comment-page-1#comment-13556</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Sun, 02 Aug 2009 04:57:13 +0000</pubDate>
		<guid isPermaLink="false">http://michaelshadle.com/?p=215#comment-13556</guid>
		<description>It will be separate like spawn-fcgi, however, it will still be a single daemon with multiple pools - something spawn-fcgi doesn&#039;t do (without custom scripts), and it will still provide all the same PHP-FPM benefits.

I want to investigate if there is a way to rip out the FastCGI requirements from the ./configure and make of a vanilla PHP build and throw it into a specific version of this new PHP-FPM, so it doesn&#039;t even need PHP sources to build in the future. Basically treat PHP like an external library at that point.</description>
		<content:encoded><![CDATA[<p>It will be separate like spawn-fcgi, however, it will still be a single daemon with multiple pools - something spawn-fcgi doesn't do (without custom scripts), and it will still provide all the same PHP-FPM benefits.</p>
<p>I want to investigate if there is a way to rip out the FastCGI requirements from the ./configure and make of a vanilla PHP build and throw it into a specific version of this new PHP-FPM, so it doesn't even need PHP sources to build in the future. Basically treat PHP like an external library at that point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://michaelshadle.com/2009/07/31/php-530-patch-now-considered-stable/comment-page-1#comment-13554</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Sun, 02 Aug 2009 03:58:55 +0000</pubDate>
		<guid isPermaLink="false">http://michaelshadle.com/?p=215#comment-13554</guid>
		<description>Nice to see the php-fpm project active again! When you say php-fpm will no longer be a patch and it&#039;ll become a standalone, do you mean that it&#039;ll be a separate application similar to spawn-fcgi?</description>
		<content:encoded><![CDATA[<p>Nice to see the php-fpm project active again! When you say php-fpm will no longer be a patch and it'll become a standalone, do you mean that it'll be a separate application similar to spawn-fcgi?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

