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" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> 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
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
