Ivan Ristic wrote:
IMHO this is a last-resort safeguard to prevent a system from falling due to badly written applications. But this can not be a reason for deciding on the architecture.From the web serving point of view it isn't. Since Apache usually interfaces to all kinds of modules and programs, the fact that processes die naturally from time to time helps remove cumulative errors.
It's not a minor issue. Using persistent objects that are expensive to aquire is a common pattern, which can improve performance significantly. The above scenario prevents exactly that.From the PHP point of view, you can get problems with persistent database connections on a very high load site, that's true. But that's about the only problem. Sure, you can't build a persistent storage of information in the server but that's a minor issue.
I guess this is more of an apache issue then a PHP issue. I'd have to look more closely at the apache sources to investigate further.
correctly and handle multithreading - is simply not worth it.
By my measurements, it is worth it.
(BTW, isn't nsapi the API for the Netscape web server?)
Yes, it is. Akos -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
