Well, you are correct that the size of the executable is irrelevant, but having different instances of PHP means less shared pages when multiple copies are loaded. There is a definite advantage to having a single httpd binary that is the same for everyone when it comes to runtime memory usage.
-Rasmus On Fri, 3 May 2002, Preston L. Bannister wrote: > From: Zeev Suraski [mailto:[EMAIL PROTECTED]] > > IMHO, the enemy of the good is the better. > > We can implement the binary-dir solution in no time, and it covers >95% of > > the problems easily, but instead we'll be discussing perfect solutions and > > end up doing nothing :) > > Yes, please! :) > > Remember KISS ... (and I'm not getting over-friendly here). > > In fact you can get pretty near 100% with the simple solution just by having > multiple copies of the PHP executable in different directories - one for each > differing configuration. On modern disks the size of PHP is insignificant, > so having multiple copies is a non-issue. > > In fact this is an advantage. If (say) you are running multiple PHP-based > web applications, each requiring different configurations, you may in fact > be dependent on different versions of PHP. A good, careful sysadmin will > want to upgrade one application at a time (and test!) rather than all at > once, and will want each application using it's own PHP executable. > > IMHO the more complicated solutions aren't really needed. > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
