<?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: eAccelerator PHP Extension Isn&#8217;t Thread-Safe&#8230;</title>
	<atom:link href="http://neosmart.net/blog/2007/eaccelerator-php-extension-isnt-thread-safe/feed/" rel="self" type="application/rss+xml" />
	<link>http://neosmart.net/blog/2007/eaccelerator-php-extension-isnt-thread-safe/</link>
	<description>Connecting Ideas</description>
	<lastBuildDate>Sat, 07 Nov 2009 18:31:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jason Lester</title>
		<link>http://neosmart.net/blog/2007/eaccelerator-php-extension-isnt-thread-safe/#comment-398070</link>
		<dc:creator>Jason Lester</dc:creator>
		<pubDate>Sat, 11 Apr 2009 08:20:51 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/2007/eaccelerator-php-extension-isnt-thread-safe/#comment-398070</guid>
		<description>@Mahmoud Al-Qudsi

I do a lot of core customization as well as sapi development in PHP (the interpreter, not scripting.) I can respect that you are a knowledgeable coder from the projects that you have done, but you seem to know little about PHP internals. You should look more deeply into the subject more before writing more posts about the &#039;lies&#039; and &#039;pretending&#039; associated with PHP threading.

There is usually five parts to a PHP solution. A server, a server to PHP interface, the PHP library, PHP extension interfaces, and extension libraries. Each of these parts are often developed by different groups/individuals and they often don&#039;t play well with each other. If even one of them is not threadsafe it will break the whole system. The PHP lib is threadsafe, and most servers are as well, but many SAPIs are not, and many extensions are not.

From what I have seen and *experienced*, the only threadsafe SAPI that ships with PHP is the Fastcgi SAPI. All others will break if they are threaded.

If the SAPI and PHP threads successfully, extension interfaces and/or extension libraries can still break the parent process if they are not thread safe.</description>
		<content:encoded><![CDATA[<p>@Mahmoud Al-Qudsi</p>
<p>I do a lot of core customization as well as sapi development in PHP (the interpreter, not scripting.) I can respect that you are a knowledgeable coder from the projects that you have done, but you seem to know little about PHP internals. You should look more deeply into the subject more before writing more posts about the &#8216;lies&#8217; and &#8216;pretending&#8217; associated with PHP threading.</p>
<p>There is usually five parts to a PHP solution. A server, a server to PHP interface, the PHP library, PHP extension interfaces, and extension libraries. Each of these parts are often developed by different groups/individuals and they often don&#8217;t play well with each other. If even one of them is not threadsafe it will break the whole system. The PHP lib is threadsafe, and most servers are as well, but many SAPIs are not, and many extensions are not.</p>
<p>From what I have seen and *experienced*, the only threadsafe SAPI that ships with PHP is the Fastcgi SAPI. All others will break if they are threaded.</p>
<p>If the SAPI and PHP threads successfully, extension interfaces and/or extension libraries can still break the parent process if they are not thread safe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mahmoud Al-Qudsi</title>
		<link>http://neosmart.net/blog/2007/eaccelerator-php-extension-isnt-thread-safe/#comment-135752</link>
		<dc:creator>Mahmoud Al-Qudsi</dc:creator>
		<pubDate>Mon, 14 Apr 2008 05:26:34 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/2007/eaccelerator-php-extension-isnt-thread-safe/#comment-135752</guid>
		<description>It turns out PHP itself is &lt;em&gt;also&lt;/em&gt; not thread-safe (even though they pretend it is):

http://neosmart.net/blog/2008/dont-believe-the-lies-php-isnt-thread-safe-yet/</description>
		<content:encoded><![CDATA[<p>It turns out PHP itself is <em>also</em> not thread-safe (even though they pretend it is):</p>
<p><a href="http://neosmart.net/blog/2008/dont-believe-the-lies-php-isnt-thread-safe-yet/" rel="nofollow">http://neosmart.net/blog/2008/dont-believe-the-lies-php-isnt-thread-safe-yet/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hydn</title>
		<link>http://neosmart.net/blog/2007/eaccelerator-php-extension-isnt-thread-safe/#comment-135682</link>
		<dc:creator>hydn</dc:creator>
		<pubDate>Mon, 14 Apr 2008 04:14:57 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/2007/eaccelerator-php-extension-isnt-thread-safe/#comment-135682</guid>
		<description>xcache is pretty much the ONLY choice.</description>
		<content:encoded><![CDATA[<p>xcache is pretty much the ONLY choice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: XCache and eAccelerator WP Plugins Updated &#x2014; The NeoSmart Files</title>
		<link>http://neosmart.net/blog/2007/eaccelerator-php-extension-isnt-thread-safe/#comment-72141</link>
		<dc:creator>XCache and eAccelerator WP Plugins Updated &#x2014; The NeoSmart Files</dc:creator>
		<pubDate>Thu, 22 Nov 2007 20:08:17 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/2007/eaccelerator-php-extension-isnt-thread-safe/#comment-72141</guid>
		<description>[...] (worker_mpm, PHP as ISAPI, PHP as NSAPI, etc.) extension to your application server (which isn&#039;t recommended with [...]</description>
		<content:encoded><![CDATA[<p>[...] (worker_mpm, PHP as ISAPI, PHP as NSAPI, etc.) extension to your application server (which isn&#8217;t recommended with [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BlueHost-Wordpress Account Is Exceeding CPU Quota? &#124; Insights, Inspiration, Tranquility, Peace and Harmony</title>
		<link>http://neosmart.net/blog/2007/eaccelerator-php-extension-isnt-thread-safe/#comment-65171</link>
		<dc:creator>BlueHost-Wordpress Account Is Exceeding CPU Quota? &#124; Insights, Inspiration, Tranquility, Peace and Harmony</dc:creator>
		<pubDate>Thu, 08 Nov 2007 13:40:27 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/2007/eaccelerator-php-extension-isnt-thread-safe/#comment-65171</guid>
		<description>[...] (worker_mpm, PHP as ISAPI, PHP as NSAPI, etc.) extension to your application server (which isn’t recommended with [...]</description>
		<content:encoded><![CDATA[<p>[...] (worker_mpm, PHP as ISAPI, PHP as NSAPI, etc.) extension to your application server (which isn’t recommended with [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eAccelerator PHP Extension Isn&#8217;t Thread-Safe&#8230; at The NeoSmart Files</title>
		<link>http://neosmart.net/blog/2007/eaccelerator-php-extension-isnt-thread-safe/#comment-48542</link>
		<dc:creator>eAccelerator PHP Extension Isn&#8217;t Thread-Safe&#8230; at The NeoSmart Files</dc:creator>
		<pubDate>Tue, 11 Sep 2007 13:11:43 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/2007/eaccelerator-php-extension-isnt-thread-safe/#comment-48542</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] eAccelerator PHP Extension Isn&#8217;t Thread-Safe&#8230;   Published September 10th, 2007  in Programming, Software, Windows Tags: Apache, APC, Bugs, eAccelerator, FastCGI, IIS, PHP, Servers, Windows, XCache [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><!--%kramer-ref-pre%-->[...] eAccelerator PHP Extension Isn&#8217;t Thread-Safe&hellip;   Published September 10th, 2007  in Programming, Software, Windows Tags: Apache, APC, Bugs, eAccelerator, FastCGI, IIS, PHP, Servers, Windows, XCache [...]<!--%kramer-ref-post%--></p>
]]></content:encoded>
	</item>
</channel>
</rss>
