> > What is your reason for picking Apache2 over Apache1.3 at this point?
> I read through the latest discussion on PHP GENERAL list. If there are > some libs having problems, with thread-safetiy..., why not using a > PHP-Installation without these libs? If they become tread-safe they can > be added again. Because there are more reasons for Apache2: That assumes we know which libraries have problems. We do not. And that is the real problem. Thread safety problems only really occur when you put a system under load and when the occur the symptoms are erratic and not very reproducable leading to weird and wonderful things happening. The prospect of having a lot of people using PHP under Apache2 with a threaded mpm and linking in all sorts of libraries of unknown thread safety does not fill me with the warm and cozies. Getting hundreds of bug reports that say that every now and then something is breaking, and it breaks in different ways all the time is not something I am looking forward to. > _Most_ ISPs(same in english? means Internet-Service-Providers) only use > PHP in CGI-Version because PHP module-Version is not secure if you have > different users on one Apache/PHP installation. With Apache 1 there was > no way to handle that, just using CGI-Version, but in Apache 2 there > _is_ this great possibility, but it can't be used because PHP only works > in Apache's prefork-mode without problems. That seems to be an Apache 1 > with less modules... as real Apache1. You are talking about the perchild mpm? That is complete vaporware. It simply doesn't work! When/if that mpm actually works, then yes, I agree, there is some real motivation to start trying to solve this impossible problem. > It is not only that Apache 2 ist faster, everybody could use PHP in > Module-Version, which is _much_ faster and offers more > possibilities(pconnect, http_auth...). Again, perchild is a dream. It doesn't really exist! -Rasmus -- PHP Install Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
