On Tue, Aug 25, 2009 at 1:09 AM, Edward Z. Yang<ezy...@mit.edu> wrote: > Excerpts from Pierre Joye's message of Mon Aug 24 18:21:32 -0400 2009: >> Please point out the differences and list what else you may need. I do >> not think we will introduce another feature but improve the current >> implementation. > > As I understand it, the features are not compatible. One takes an > explicit list of directories to scan, while the other dynamically > determines it based on the current working directory and the > user's home directory. (There are some other features on top > of this, but that's the essential functionality). Please let me > know if I am mistaken.
There is two modes: - It looks in the current directory for ini file (named by default .user.ini) and scan the parent directories up to the document root to apply rules from other .user.ini. - new directives in php.ini using sections, like [PATH=/home/www/site1] or [HOST=...] >> It is easy to make htscanner support ini format instead :) > > That is true. However, it would be nice to see this go into the > core, so as to encourage wide use (also, htscanner is something > of a hack, quite frankly.) It is in the core now, and from an implementation point of view there are very few differences. 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
