On Mon, Apr 22, 2002 at 04:01:25PM -0400, Jim Jagielski wrote: > Right now, we assume that each successive use of PHPINIDir is > due to its inclusion in a <VirtualHost container>. I wonder if > that's overly restrictive... Should we allow successive uses and > just honor the last one?
Since the PHPINIDir is supposed to be a per-server config directive, it should only occur in the global config or in a vhost config. Ultimately I think this directive should be able to apply per-vhost, but at the moment that isn't possible. The problem is that we can only initialize with one php.ini, but at module startup time (for us this is post_config) we don't know which vhost we'd like to serve. I think the problem will become more apparent as the perchild MPM becomes more mature, so for now I just kept it as simple as possible and disallowed attempts at per-vhost configs. -aaron -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
