Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:45376
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.212 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=nQumj0l8ManwOyDZavJ13JsMIh89i8Q8nZMxfeqQRgV6SnpGBFh85mxD05QpP0VyR1
         GQ6U24ystQBtSFPDthXCWesrqUhfw0XBZMQbEjMWcG1E3pUfKuq0JPoVkffEgrnjpXSZ
         V2ByEqz3CSFskFaXnDa3aObJvCsNKaZVQRnsc=
MIME-Version: 1.0
In-Reply-To: <1251153827-sup-3119@javelin>
References: <1251149348-sup-4709@javelin>
	 <fe05d1540908241503w6de49c48uf41094e62f08a2d8@mail.gmail.com>
	 <1251151666-sup-9840@javelin>
	 <fe05d1540908241521m6195bf7cs750a0a49b5369486@mail.gmail.com>
	 <1251153827-sup-3119@javelin>
Date: Tue, 25 Aug 2009 01:37:38 +0200
Message-ID: <fe05d1540908241637p3a0c0da2id2bbb6e3090adf11@mail.gmail.com>
To: "Edward Z. Yang" <ezyang@mit.edu>
Cc: internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Per-directory PHP configuration
From: pierre.php@gmail.com (Pierre Joye)

On Tue, Aug 25, 2009 at 1:09 AM, Edward Z. Yang<ezyang@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. =A0One 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. =A0(There are some other features on top
> of this, but that's the essential functionality). =A0Please 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=3D/home/www/site1] or [HOST=3D...]

>> It is easy to make htscanner support ini format instead :)
>
> That is true. =A0However, 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,
--=20
Pierre

http://blog.thepimp.net | http://www.libgd.org