Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32234
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.187 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=DVxHLxKYauDwp9z1RwxwXK8CTFYk3+FiHzC/fnKSWVzHpAEjDWVwExYku9VY9lPHzddvqLpovyX5WnJ48zEGCjWpCkATNQRCYKWYbrNKiJ+QXB24Q4K1w+funbU8GTr52YDIvSIS78QKFG21ujWQeKHYUdTNiNp9StF4UnZJ1IQ=
Message-ID: <fe05d1540709110111o515694c0o61c1474b30f17e57@mail.gmail.com>
Date: Tue, 11 Sep 2007 10:11:27 +0200
To: jani.taskinen@iki.fi
Cc: "Andi Gutmans" <andi@zend.com>, "Ilia Alshanetsky" <ilia@prohost.org>, 
	"PHP Developers Mailing List" <internals@lists.php.net>
In-Reply-To: <1189498072.3319.14.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <6F509818-65A2-4B17-8C44-6970E815A169@prohost.org>
	 <698DE66518E7CA45812BD18E807866CEA2AE39@us-ex1.zend.net>
	 <fe05d1540709101356y354326bbo920c6750eeb956f2@mail.gmail.com>
	 <1189498072.3319.14.camel@localhost.localdomain>
Subject: Re: [PHP-DEV] PHP 5.3 Suggested Feature List
From: pierre.php@gmail.com (Pierre)

On 9/11/07, Jani Taskinen <jani.taskinen@sci.fi> wrote:
> On Mon, 2007-09-10 at 22:56 +0200, Pierre wrote:
> > On 9/10/07, Andi Gutmans <andi@zend.com> wrote:
> > > > 16) Introduce new php.ini files parser/scanner + CGI/FastCGI?
> > > > "htaccess" style ini file support
> > > >
> > > > 1             0               -1
> > >
> > > 0 (this can be nice but we need to make sure it's optional because those
> > > stat()'s can be very hard on performance which is why many sites turn
> > > off .htaccess).
> >
> > For the record here, a cache is planed once we have a stable version.
> > Something like what htscanner does, it already caches the entries
> > (cache + stat check once ttl is over).
>
> Just clarification: the caching is there already. :)
> But I didn't use any stat calls for sake of KISS.
> When cached results expire, the file (if it exists..) is re-scanned.
> Maybe someone has better idea. But that remains to be seen. :)

Oh damned me, I did not notice it in the patch :)

And I agree, for this feature, a cache system like this one is the
easiest way (to maintain and to keep the performance impact as a very
low level) and works well. I use such system since months with
htscanner (and some ISPs too) and did not notice a significant slow
down.

Cheers,
--Pierre