Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:48914 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 76825 invoked from network); 21 Jun 2010 11:12:36 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Jun 2010 11:12:36 -0000 Authentication-Results: pb1.pair.com header.from=mls@pooteeweet.org; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=mls@pooteeweet.org; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 188.40.37.16 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 188.40.37.16 hq1.backendmedia.com Linux 2.6 Received: from [188.40.37.16] ([188.40.37.16:38928] helo=hq1.backendmedia.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 71/AC-04713-1294F1C4 for ; Mon, 21 Jun 2010 07:12:36 -0400 Received: from localhost (unknown [127.0.0.1]) by hq1.backendmedia.com (Postfix) with ESMTP id 11D8C200C18D; Mon, 21 Jun 2010 11:12:32 +0000 (UTC) X-Virus-Scanned: amavisd-new at backendmedia.com Received: from hq1.backendmedia.com ([127.0.0.1]) by localhost (hq1.backendmedia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RUjQW6khjlSZ; Mon, 21 Jun 2010 13:12:31 +0200 (CEST) Received: from [192.168.80.154] (77-58-253-248.dclient.hispeed.ch [77.58.253.248]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mls@pooteeweet.org) by hq1.backendmedia.com (Postfix) with ESMTPSA id ACDE4200C187; Mon, 21 Jun 2010 13:12:31 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii X-Priority: 3 In-Reply-To: <5D.AB.04713.1F74F1C4@pb1.pair.com> Date: Mon, 21 Jun 2010 13:12:26 +0200 Cc: internals@lists.php.net Content-Transfer-Encoding: quoted-printable Message-ID: <7FB6E122-73CF-430E-9934-DB19F63F0978@pooteeweet.org> References: <1736FE65-C0F0-4677-919D-410C81C0FD47@macvicar.net><4C1EF360.3060902@lerdorf.com><5E.F5.04713.BD92F1C4@pb1.pair.com><50.57.04713.B513F1C4@pb1.pair.com><9B.98.04713.E173F1C4@pb1.pair.com><9D.A9.04713.E5F3F1C4@pb1.pair.com> <5D.AB.04713.1F74F1C4@pb1.pair.com> To: "jvlad" X-Mailer: Apple Mail (2.1081) Subject: Re: [PHP-DEV] APC in trunk From: mls@pooteeweet.org (Lukas Kahwe Smith) On 21.06.2010, at 13:07, jvlad wrote: > Competition between opcode caches for php will definitely be reduced = by=20 > adding APC into the core, > so the market will shrink, of course. i think this is a likely outcome indeed. it might also be phrased in a = more positive tone in that likely efforts will be joined. for example = maybe zend will decide to contribute some of their code to APC. so the key question might be more is there something in APC that makes = it fundamentally the right or wrong approach. furthermore does adding any byte code cache to core also enable new = kinds of optimizations because its now possible to more tightly = integrate with core? regards, Lukas Kahwe Smith mls@pooteeweet.org