Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65551
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain zend.com does not designate 209.85.219.46 as permitted sender)
References: <5d21b42656d49b4a71d9f808541bd745@mail.gmail.com>
 <51078485.30107@rotorised.com> <11e1ccc6eca996d9d94ae9a3bff0bbab@mail.gmail.com>
 <5108667C.1030901@oracle.com> <510868DE.7010408@lerdorf.com>
 <5108749D.8090608@oracle.com> <20d0caac77a46de19086bb6ab622be6f@mail.gmail.com>
 <510B6536.8050901@oracle.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <510B6536.8050901@oracle.com>
Date: Fri, 1 Feb 2013 10:38:48 +0200
Message-ID: <7113676647725427046@unknownmsgid>
To: Christopher Jones <christopher.jones@oracle.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=e89a8ff1c2fc55de9904d4a5ac64
Subject: Re: [PHP-DEV] [RFC] Integrating Zend Optimizer+ into the PHP distribution
From: zeev@zend.com (Zeev Suraski)

--e89a8ff1c2fc55de9904d4a5ac64
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Chris,

We're talking about a very specialized piece of software - an opcode cache
- nothing more, nothing less.  It's not going to do anything beyond
implementing the concept of an opcode cache in php - no extra features.
Rasmus pointed out correctly that this component has nothing to do with the
Optimizer (sans +).  It will also not have any special interaction with
Zend Guard, beyond perhaps the same mechanisms I mentioned might be useful
for debuggers (controlling the order of compile/exec callbacks, already in
the RFC).  Supporting Zend Guard would be Zend's headache - not php.net's -
and wouldn't require any special treatment.

At the end of the day it's supposed to integrate cleanly into php without
any negative impact - not on functionality nor compatibility.

In terms of what integration would entail - my intent was that integration
means that it's on by default.  I'll clarify that in the RFC, unless people
think we should put that up for discussion..?

Sent from my mobile

On 1 =D7=91=D7=A4=D7=91=D7=A8 2013, at 08:48, Christopher Jones <christophe=
r.jones@oracle.com>
wrote:



On 01/30/2013 06:47 AM, Zeev Suraski wrote:

This is the kind of info the RFC (and then user doc) should have.


I updated the RFC with two extra sections - 'what's an opcode cache',


This section extremely general and doesn't explain what the expected
feature set might look like.  I'm not asking for absolute certainties,
just a technical description of what is and isn't the goal. Is it the
complete Optimizer+, are there potential cleanups, do you see it being
enabled (if not in PECL) or disabled by default, etc.

Did I miss seeing the link to the current optimizer+ documentation?
http://files.zend.com/help/previous-version/Zend-Server-5-Community-Edition=
/zendoptimizerplus.html
(thanks Rasmus)

Your email comment to John Carter about Zend Guard decoder is also not
(yet) in the RFC.

Chris

and 'interaction with other plugins'.


https://wiki.php.net/rfc/optimizerplus


Zeev



--=20
christopher.jones@oracle.com  http://twitter.com/ghrd
Newly updated, free PHP & Oracle book:
http://www.oracle.com/technetwork/topics/php/underground-php-oracle-manual-=
098250.html

--e89a8ff1c2fc55de9904d4a5ac64--