Re: [PHP4BETA] Re: [PHP-DEV] Should php3_fopen_for_parser change the current working directory?

From: Date: Wed, 24 Nov 1999 13:41:19 +0000
Subject: Re: [PHP4BETA] Re: [PHP-DEV] Should php3_fopen_for_parser change the current working directory?
References: 1 2  Groups: php.dev php.version4 
Request: Send a blank email to php-dev+get-13057@lists.php.net to get a copy of this message
On Wed, Nov 24, 1999 at 02:30:11PM +0100, Thies C. Arntzen wrote: > On Wed, 24 Nov 1999, Sascha Schumann wrote: > > > > add NO_GLOBAL_LOCK to you CFLAGS - right now there's a global lock in > > > main.c. (sascha put it in for some reason i forgot - maybe 'cause it > > > wasn't as stable on with aolserver as we thought) > > > > If the module does not work in ZTS mode, NO_GLOBAL_LOCK does > > nothing. > > right, but i think that the plan should be to be able to run in ZTS mode > without GLOBAL_LOCK? the roxen module (like aolserver and zeus) should > run in ZTS and should allow more that one page at a time. I agree with that; the problem here is that a SAPI module developer would have to track two moving targets. The first one is PHP, the second one is the SAPI module. For debugging, this is a ridiculous situation, because problems might be caused by PHP or the SAPI module. The global lock disables multi-threaded execution of scripts, therefore avoiding the thread-safety issues of PHP. -- Regards, Sascha Schumann Consultant

« previous php.dev (#13057) next »