I also prefer configuration files over registry. Andi
At 11:04 01/05/2002 -0700, Preston L. Bannister wrote: >From: Daniel Beulshausen [mailto:[EMAIL PROTECTED]] > > > > At 18:35 01.05.2002 +0200, Sebastian Bergmann wrote: > > >Daniel Beulshausen wrote: > > > > do you mean constants like PHP_EXTENSION_DIR? > > > > > > For instance, yes. > > > > > > > they should be changed to use the windows registry anyway... > > > > > > Feel free to do it :) > > > > this isn't going to be a big task, i'll put it onto my todo. > > >I'd rather strongly suggest this value not be in the registry. > >What happens in the case were two different applications are installed >on the same machine, and both use PHP - but different versions and with >different libraries? You really don't want machine-global settings. > >This isn't a theoretical question! :) > >We will be using PHP in our application and need to be certain that >any changes the customer makes to there global use of PHP does not >crater out application. We can get this assurance by using a local >copy of PHP in our application, with a local "php.ini" file. > >Instead I'd suggest that the settings stay in php.ini, but that PHP >look for php.ini first local to the installation of php.exe. > >I posted a (tested!) patch a few days back to do exactly this. > >-- >Preston L. Bannister >http://members.cox.net/preston.bannister/ >pbannister on Yahoo Messenger > >-- >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
