Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65184 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 98112 invoked from network); 25 Jan 2013 18:48:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Jan 2013 18:48:43 -0000 Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain zend.com does not designate 209.85.219.51 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.219.51 mail-oa0-f51.google.com Received: from [209.85.219.51] ([209.85.219.51:41002] helo=mail-oa0-f51.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D8/63-14132-A83D2015 for ; Fri, 25 Jan 2013 13:48:43 -0500 Received: by mail-oa0-f51.google.com with SMTP id n12so833178oag.24 for ; Fri, 25 Jan 2013 10:48:39 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:references:in-reply-to:mime-version:x-mailer :thread-index:date:message-id:subject:to:cc:content-type :x-gm-message-state; bh=vnQIY8IQOgs4NKgOjfv+pa65+yezLaonFLz1cauqywA=; b=lHL96WW8kTYJ6nQEXLjyvimCeohMj7/eB02KRN4/t3xIHBirpDcRVGsSYf+JDMYTvH qWKf8EjVvYW+1rLqnVKIcQWaOZORpuz01sXfNIT8mkMbsvmcbmpnxvHze16QNRVSgbBu phQpR8mVe0qiWeifSsO5/td5kDMtDXsd/WmigBvlsM6zFwQw2/e/InU62p8oa2i3bais 2kccXkRLSq1gA5kw/v8Eix83Y1cgbSndsV+tNVmDDgyD5cPpgqeTyjta7ElxdJOYu6jO kvET82qSsKIJ6QS9aAIwkLYhXT4737o8qHg6THHDh0/mMg15RlqUgm5FkluEaBjbW1Rd JP4Q== X-Received: by 10.60.169.205 with SMTP id ag13mr5339363oec.40.1359139719688; Fri, 25 Jan 2013 10:48:39 -0800 (PST) References: <51023AB1.2010607@b1-systems.de> <51024016.4010005@lerdorf.com> In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQH5KhtP6VxxLAoJObFXtxoIw+gBzgJTObh3AnFb11YDa6R5KAFZ2VOEAfpcKa4BnViVyZea9lCg Date: Fri, 25 Jan 2013 20:48:39 +0200 Message-ID: <33ca8b76c1b1af556282cbeaa81824d4@mail.gmail.com> To: Pierre Joye Cc: Rasmus Lerdorf , Ralf Lang , PHP internals Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQm0QQUjZNAXU70Oee7lHJBKxoRcFwD7eS9gxjwAiLuObZlTYvbBX6/oPy61oubVQGYYIWc6QNIVoXcvZzt7OCKlDnmyjENif1346MPHBrec3tvFPNZ0SOa15XTtbAKoxEX/w/xZ Subject: RE: [PHP-DEV] HEADS UP: Upcoming Feature Freeze for PHP 5.5.0 From: zeev@zend.com (Zeev Suraski) > -----Original Message----- > From: Pierre Joye [mailto:pierre.php@gmail.com] > Sent: Friday, January 25, 2013 8:42 PM > To: Zeev Suraski > Cc: Rasmus Lerdorf; Ralf Lang; PHP internals > Subject: Re: [PHP-DEV] HEADS UP: Upcoming Feature Freeze for PHP 5.5.0 > > hi Zeev, > > On Fri, Jan 25, 2013 at 5:25 PM, Zeev Suraski wrote: > >> Either by a number of people stepping up to help with the existing > >> APC > > code, or > >> perhaps more realistically making it a priority in PHP 5.6 to > >> streamline > > the > >> engine and the executor for opcode caching and either including a > > heavily > >> simplified version of APC or writing a new one. > >> > >> One thing I can guarantee is that if we add it to core in its current > > condition it > >> will delay 5.5 by 6+ months if not longer. > > > > There's another option. We have the Optimizer+ component which is > > current, a bit faster than APC, worked with PHP 5.4 from the get go > > and already fully supports 5.5 - and now that it's been free for use > > for several years, we'd actually be happy to opensource it and make it > > a part of core. An extra benefit would be that we'd commit to > > maintain it, although of course, community contribution will be very welcome. > > Here too, it's code with a very long history, some of which even > > predates PHP 4.0. But It Works(tm), and we could put some effort into > > cleaning it up and beautifying it. > > Thanks, That sounds great. > > > I think we can actually do it on time for 5.5.0, or with a relatively > > minor delay that might be worth it. I'm sure most users would prefer > > the version to take a bit longer if it comes with an opcode cache > > right off the bat. > > There'll most probably be APIs we'd want to merge from APC, but doing > > that should be easy - and we can get the good of both worlds. > > Please don't bring over the user cache, please don't :-) Sounds like there's concensus we don't want these things coupled, so we should probably handle that part separately :) > > Quesiton: Does it support both NTS and TS? I think it used to but if it did that part hasn't been maintained for a very long time. Not sure where it stands right now... Zeev