Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:2924 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 63036 invoked from network); 28 Jun 2003 06:02:26 -0000 Received: from unknown (HELO www.lerdorf.com) (66.93.78.119) by pb1.pair.com with SMTP; 28 Jun 2003 06:02:26 -0000 Received: from [10.0.1.10] ([10.0.1.10]) by www.lerdorf.com (8.12.9/8.12.9/Debian-4) with ESMTP id h5S62PEa008429; Fri, 27 Jun 2003 23:02:25 -0700 Date: Fri, 27 Jun 2003 23:02:25 -0700 (PDT) To: Marc Richards cc: internals@lists.php.net In-Reply-To: <20030628055230.56980.qmail@pb1.pair.com> Message-ID: References: <20030628055230.56980.qmail@pb1.pair.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] Apache 2 support From: rasmus@lerdorf.com (Rasmus Lerdorf) On Sat, 28 Jun 2003, Marc Richards wrote: > I apologies if this is the wrong place for asking. Is non-experimental > Apache2 support planned for PHP 5? Nope. Until someone sits down and goes through every 3rd-party library that can be linked into PHP on every platform and identifies whether or not they are threadsafe and under which conditions they remain threadsafe, using PHP in a threaded web server on UNIX is going to remain experimental. You can of course stick with non-threaded prefork mode, in which case you basically have Apache-1.3.x. Nobody so far have been motivated to test Apache2-prefork+PHP extensively, so even that combination is going to remain experimental. The basic problem here is that the average UNIX library has not been written with thread safety in mind. You can write very good specific threaded programs on UNIX, but it is extremely difficult to write something which can potentially link in hundreds of random libraries and expect them to all be threadsafe. -Rasmus