On Wed, 11 Feb 2004, Ilia Alshanetsky wrote: > On February 11, 2004 10:00 am, Mehdi Achour wrote: > > Because we care about performance. Plus, if we want to have the IRCG > > feature automatically added/deleted for a customer, the two separated > > servers isn't this good solution. > > About implementing access restriction for IRCG.. I'm not sure we'd like > > to hack IRCG for each new version, or hack each extension that we > > provide this way (ircg is just an exemple) > > You could always disable a critical function of the IRCG extension, such as > the connection initialization function. This way you can effectively turn off > the extension for some virtual hosts.
disable_functions only works from php.ini AFAIK... so this doesn't work :) regards, Derick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
