2009/12/23 Tjerk Meesters <tjerk.meest...@gmail.com>: > On 24-Dec-2009, at 2:47, Pierre Joye <pierre....@gmail.com> wrote: > >> On Wed, Dec 23, 2009 at 7:20 PM, Michael Shadle <mike...@gmail.com> wrote: >>> >>> On Wed, Dec 23, 2009 at 10:13 AM, Mikko Koppanen <mkoppa...@php.net> >>> wrote: >>> >>>> Hello, >>>> >>>> I think you can use PHP_INI_SCAN_DIR environment variable which should >>>> work runtime as well. >>> >>> still seems a bit archaic. i don''t see any reason why include support >>> can't be added in php.ini. it will probably wind up becoming more >>> popular and widely used than the configure option too, or the >>> environment option... >> >> Please tell me one benefit except "we support include"? I don't see >> any. The extra files are still there, they will be loaded too, etc. >> > The most tempting reason for me would be to have easier control of what gets > loaded between SAPI's, eg load this ini for cli but not for cgi, etc. Right > now this is only possible by compiling each Sapi with its own search path, > which is more cumbersome. >> >> Cheers, >> -- >> Pierre >> >> http://blog.thepimp.net | http://www.libgd.org > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
For different SAPIs ... php-cli.ini, php-isapi.ini, php-cgi-fcgi.ini, etc. is what I use on Windows. Combined with registry settings for PHP (Prior to PHP5), PHP5 and PHP6, I can very easily dictate which INI file will be loaded for which version of PHP and for which SAPI. Beyond that, I can use [HOST=] for some host specific settings. All of this is with the standard windows pre-compiled binaries. -- ----- Richard Quadling "Standing on the shoulders of some very clever giants!" EE : http://www.experts-exchange.com/M_248814.html Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 ZOPA : http://uk.zopa.com/member/RQuadling -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
