Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:17728 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 51306 invoked by uid 1010); 9 Aug 2005 19:42:14 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 51291 invoked from network); 9 Aug 2005 19:42:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Aug 2005 19:42:14 -0000 X-Host-Fingerprint: 80.74.107.235 mail.zend.com Linux 2.5 (sometimes 2.4) (4) Received: from ([80.74.107.235:43994] helo=mail.zend.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id CF/9C-04646-51709F24 for ; Tue, 09 Aug 2005 15:42:14 -0400 Received: (qmail 7729 invoked from network); 9 Aug 2005 19:42:08 -0000 Received: from localhost (HELO ANDI-NOTEBOOK.zend.com) (127.0.0.1) by localhost with SMTP; 9 Aug 2005 19:42:08 -0000 Message-ID: <5.1.0.14.2.20050809124051.034a49a0@localhost> X-Sender: andi@localhost X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 09 Aug 2005 12:42:08 -0700 To: "Ron Korving" ,internals@lists.php.net In-Reply-To: <7F.53.04646.A53E8F24@pb1.pair.com> References: <57792e85050808205143e96a8f@mail.gmail.com> <42F82AE3.6070602@lerdorf.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: [PHP-DEV] Moving to PHP5.1 and Apache 2.2 next year, need help From: andi@zend.com (Andi Gutmans) We've made a start a long time ago, and we do our best to keep all of PHP thread-safe. On paper it is. When a bug appears we fix it. Is it a risk to run it... I think it is but I have seen people running it successfully on IIS for a long time. (I still think that's a bad idea though). Andi At 07:09 PM 8/9/2005 +0200, 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... > >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 > >-- >PHP Internals - PHP Runtime Development Mailing List >To unsubscribe, visit: http://www.php.net/unsub.php