httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "NAIK,ROSHAN (HP-Cupertino,ex1)" <>
Subject RE: story posted
Date Fri, 07 Feb 2003 00:00:08 GMT

Rather than fix the TS issues in all the 3rd party libraries that can be
with PHP's and its extension its more pragmatic to sort out thread/filter
in PHP core. Since similar arguments can be made for Apache core too.
The same issue has certainly not stopped Apache 2.0 itself from going
forward with
full thread support. Apache core minds its own threading business and lets
all the 
modules to mind (or not mind) their own ...despite the fact that using such
modules renders Apache server on a users m/c susceptible to the threading
related disasters.

Also blaming on use of TLS seems a little strange since use of TLS is
supposed to improve re-entrancy
isn't it ? 

Also the /tmp/somefile  implementation that sascha was referring to was
changed many releases ago.

Given the availablity of TSRM (Thread safe resource manager) on PHP seems
like a attempt 
in the direction. So is the thread safety issue exist due to not using TSRM
where needed within
PHP or cuz TSRM needs more work and there is more to it than just TSRM ?


> -----Original Message-----
> From: Rasmus Lerdorf []
> Sent: Thursday, February 06, 2003 2:06 PM
> To:
> Subject: Re: story posted
> > Perhaps it's best for someone to simply port php4apache to 
> 2.0 and start
> > moving a little momentum.  The thread-safety arguement is a 
> little bogus,
> > until folks have something to start finding thread-safety 
> bugs.  How long
> > have Win32 users been doing PHP within threaded servers?
> We have gotten a number of TS bug reports, and what does 
> Windows have to
> do with it?  Most Windows libraries are threadsafe to begin 
> with.  We are
> not talking about TS issues in PHP here, we are talking about them in
> libraries that we have no control over.  Sometimes these are even
> binary-only libraries.  This is something that will 
> eventually work itself
> out as developers become more aware and threaded apps start 
> becoming more
> common on UNIX systems.  But that doesn't change the fact that it is a
> real problem for us today.
> I would love to have a list of the known TS issues in the various
> 3rd-party libraries out there, and I did try to push that a 
> bit with this:
> a while ago now.  I was hoping for some more input here.  We should be
> able to get to the point where we can tell people that 
> Apache2+PHP+"List
> of safe extensions" is production-quality as long as they 
> don't stray into
> any of the extensions/3rd party libs on the unsafe/unknown 
> list.  Right
> now that list unfortunately includes just about everything 
> you can hook
> into PHP.
> -Rasmus

View raw message