Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:36163
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.162 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 17 Mar 2008 09:59:46 +0200
Message-ID: <06B0D32C7A96544490D18AF653D6BDE502759904@il-ex1.zend.net>
Thread-Topic: [PHP-DEV] Patch for opcode caches
Thread-Index: AciGBz6n8Se8bzEfScSGR9WKjfZK5AB/SUkQ
To: "Stas Malyshev" <stas@zend.com>,
	"Rasmus Lerdorf" <rasmus@lerdorf.com>
Cc: "Marcus Boerger" <helly@php.net>,
	"Andi Gutmans" <andi@zend.com>,
	<internals@lists.php.net>
Subject: RE: [PHP-DEV] Patch for opcode caches
From: dmitry@zend.com ("Dmitry Stogov")



> -----Original Message-----
> From: Stanislav Malyshev [mailto:stas@zend.com]=20
> Sent: Friday, March 14, 2008 10:11 PM
> To: Rasmus Lerdorf
> Cc: Marcus Boerger; Dmitry Stogov; Andi Gutmans;=20
> internals@lists.php.net
> Subject: Re: [PHP-DEV] Patch for opcode caches
>=20
>=20
> > I don't actually see early binding as being much of a problem, the=20
> > real
> > problem is when the same class is both early and late=20
> bound.  If you=20
> > consistently always bind early or always bind late, opcode=20
> caches should=20
> > be quite happy to let you do that.  But if you mix the two,=20
> things get=20
>=20
> That's what we try to do in this patch - to make cache able to change=20
> the binding mode.

Exactly. With very small opcode cache modification, it will able to work
exactly in the same way as PHP works without any caches. The
early-binding will be performed not in compile-time, but in
file-load-from-cache-time.

Thanks. Dmitry.