Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:17707
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: internals@lists.php.net
Date: Tue, 9 Aug 2005 19:23:10 +0200
User-Agent: KMail/1.8
Cc: "Ron Korving" <r.korving@xit.nl>
References: <57792e85050808205143e96a8f@mail.gmail.com> <42F82AE3.6070602@lerdorf.com> <7F.53.04646.A53E8F24@pb1.pair.com>
In-Reply-To: <7F.53.04646.A53E8F24@pb1.pair.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-ID: <200508091923.10971.johannes@php.net>
Subject: Re: [PHP-DEV] Moving to PHP5.1 and Apache 2.2 next year, need help
From: johannes@php.net (Johannes Schlueter)

Hi Ron,

On Tuesday 09 August 2005 19:09, Ron Korving wrote:
> Nonetheless, Rasmus, isn't it something to work on? Like Steve said, #1 and
> #2 can be accomplished, and that would at least be a good start. You are
> right about the libraries, but in time, even these may become thread safe
> (of course, likely not by anyone from the PHP-community). Why is this
> thread-safety such a taboo for many of the people here? Don't get me wrong,
> I know it can't be done in one go, but a start could be made, right?
> Perhaps that start could be made from PHP6 on? It doesn't have to be
> officially thread safe, because of all the libraries, but it could be
> thread-safer...

PHP itself is thread-safe. The problem is in the libraries. Rasmus once wrote 
a nice mail to this list about these problems: 
http://news.php.net/php.internals/10491

johannes