Yes, I do completely understand the problems in ensuring thread-safeness ... I've done it myself before for a secure system, where we had to scan complete code for knowing what was thread-safe, and what wasn't.
Having to do that for multiple machines, is even worse, so I can definitely understand the problems that will be encountered. Hence my asking if there was a large effort being put towards it, and wondering what a timeline of said effort is. Obviously, I have my answer, that there isn't a large effort, and that there isn't a timeline. It's going to be catch as catch can ... Which is fine ... It just seriously dampens my own ability to run Apache2, given our reliance upon PHP4, which puts me into a catch22 situation that I will need to solve. Eli At 01:10 PM 5/13/2002 -0700, Rasmus Lerdorf wrote: >The question is how one would certify an extension? You can't just look >at the code for 3 minutes and say, yup, this is threadsafe. I mean, you >can probably do that on the PHP-side of things, but what about the real >code in the 3rd-party library? And even if the library claims to be >threadsafe, is it really? And are there any caveats? This is going to >take some time. [snip..] -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
