Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81677
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.45 as permitted sender)
References: <008b01d03f06$bc8e9940$35abcbc0$@tekwire.net> <54CFAAA5.6050700@lerdorf.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <54CFAAA5.6050700@lerdorf.com>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-ID: <24F6AFBF-11C0-48C2-A923-87A79A475792@gmail.com>
Cc: "francois@tekwire.net" <francois@tekwire.net>,
 "internals@lists.php.net" <internals@lists.php.net>
Date: Tue, 3 Feb 2015 14:35:27 +1100
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Subject: Re: [PHP-DEV] [VOTE] Add is_cacheable() stream-wrapper operation
From: davidkmuir@gmail.com (David Muir)



> On 3 Feb 2015, at 3:49 am, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
>=20
>> On 02/02/2015 08:38 AM, Fran=C3=A7ois Laupretre wrote:
>> Hi,
>>=20
>> Opening the vote for :
>>=20
>> https://wiki.php.net/rfc/streams-is-cacheable
>>=20
>> This RFC proposes a generic way for opcode caches to decide if a given UR=
I
>> is cacheable or not.
>=20
> Doesn't this imply that "path" is the one true cache key? There are some
> issues with that which we will have to address at some point. For
> example, when running fpm chrooted you need more than the path. We'll
> likely need a more APC-like option here to use the device+inode for the
> key. It seems like a generic mechanism like you are proposing needs to
> take this into account and provide some mechanism that tells the opcode
> cache how to determine uniqueness. Perhaps that is simply encoded into
> the path parameter, but then maybe it should have a more appropriate name.=

>=20
> -Rasmus
>=20
>=20

Don't we already have this problem with chrooted FPM? I haven't tested it mo=
re recently, but last time I tried, opcache would fail to invalidate the cac=
he after updating the file. Worked fine with a non-chroot environment. Not s=
ure if this is related to the issues you mean here...=