On Thu, 23 Jan 2003, Jean-Christian Imbeault wrote: > Rasmus Lerdorf wrote: > > > > No, you didn't understand correctly. I specifically said the thread > > safety issues were in 3rd party libraries and not in PHP. > > Sorry, I thought by 3rd party libraries you meant libraries that PHP is > dependent upon. Do you mean libraries used by PHP or Apache. And if > these are libraries used by PHP, do you mean library that as in the > multi-byte library (i.e. libraries that add functionality to PHP), or do > you mean C libraries used when compiling PHP.
Common libraries such as gdbm or c-client, for example. > So this boils down to Apache2 using threads and PHP not being thread-safe? No > And the reason that PHP is not thread-safe is that some 3rd party > libraries PHP used are not thread-safe. No > If they are libraries used to compile PHP, I would assume that Apache2 > must have faced similar issues when going from a forking model to a > threaded model? Why? Apache by itself doesn't need to talk to anywhere near the same number of 3rd-party things that PHP commonly talks to. > #2 Is there progress being made towards having PHP work with Apache2. > And who is working on this (if not the PHP team). Nobody really is. And I don't see this changing until there are some really compelling features in Apache2 to warrant the massive effort it would take. And yes, a working perchild mpm may be that compelling feature, but we don't have one of those. All of this stuff is available by reading the PHP and Apache dev lists, by the way. They are archived and not that hard to find. -Rasmus -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
