7/9/01 9:00:21 PM, Zeev Suraski <[EMAIL PROTECTED]> wrote:

>At 21:55 9/7/2001, Thies C. Arntzen wrote:
>>On Mon, Jul 09, 2001 at 09:47:46PM +0300, Zeev Suraski wrote:
>> > Remember that while this is an impressive improvement, it's not all that
>> > useful in the vast majority of cases (it's especially useful with Apache
>> > 2.0).
>>     IIS comes to mind - aolserver, fasttrack and maybe a few
>>     more.
>In terms of performance?  I don't recall seeing any production sites 
>running on the threaded version of PHP as of yet

...because there might be some issues to be addressed yet. I have 
posted here previously some moanings (sorry) about PHP, persistent
database connections and multithreaded webservers... this is where 
PHP really makes the webservers scream... 

sorry but I'm not going to stop moaning :-)

some examples: multithreaded Apache (latest 1.3.x versions 
at least, don't know about 2.0.x) does not apply because it spawns 
threads instead processes but that's all, new PHP global structures 
are allocated per thread, so great deal !. 

don't even think of IIS-ISAPI, some more semaphores are needed
before we can pull several database-driven scripts at the same time without

and so on...

7/9/01 9:31:47 PM, Zeev Suraski <[EMAIL PROTECTED]> wrote:

>Uhm, being the guy that made PHP thread safe and implemented the first 
>multithreaded SAPI, I'd say I do too.  It doesn't mean I don't realize it's 
>currently not being actively used, though.

so !, there are many corners we can cut here, for example, the
multithreaded/persistent DB connections stuff and others. 
We are just willing to help!

Isn't those technical issues much more important? Come on!

Thanks for reading,

F.J. Ortiz

PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to