Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:17704 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 74140 invoked by uid 1010); 9 Aug 2005 17:09:46 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 74125 invoked from network); 9 Aug 2005 17:09:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Aug 2005 17:09:46 -0000 X-Host-Fingerprint: 212.238.144.71 korving.demon.nl Received: from ([212.238.144.71:1778] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 7F/53-04646-A53E8F24 for ; Tue, 09 Aug 2005 13:09:46 -0400 Message-ID: <7F.53.04646.A53E8F24@pb1.pair.com> To: internals@lists.php.net References: <57792e85050808205143e96a8f@mail.gmail.com> <42F82AE3.6070602@lerdorf.com> Date: Tue, 9 Aug 2005 19:09:12 +0200 Lines: 30 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Posted-By: 212.238.144.71 Subject: Re: [PHP-DEV] Moving to PHP5.1 and Apache 2.2 next year, need help From: r.korving@xit.nl ("Ron Korving") 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... Ron "Rasmus Lerdorf" wrote in message news:42F82AE3.6070602@lerdorf.com... > steve roussey wrote: > > I have read and understand that there are a number of issues: > > > > 1. Problems with the Apache2 sapi > > 2. Problems with thread safety in the Zend Engine or PHP itself > > 3. Problems with thread-safety of modules > > You missed the most serious one. Thread safety problems in random > libraries you link in and we have absolutely no control over those. > > My stuff is far bigger and busier than yours, and I have absolutely no > intention to go threaded anytime soon. > > -Rasmus