Re: APC in trunk
| From: | Ilia Alshanetsky | Date: | Mon, 21 Jun 2010 03:39:30 +0000 |
| Subject: | Re: APC in trunk | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-48884@lists.php.net to get a copy of this message | ||
Stas,
If there is a better alternative to APC we can bundle with PHP, I am
definitely open to exploring that idea. However the alternatives I am
familiar either are closed source or have licences incompatible with
PHP, and that's without getting into the "better" argument.
On Sun, Jun 20, 2010 at 11:31 PM, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> Hi!
>
>> The point is that it would be there for people to use, with as little
>> effort as possible, which would be changing 1 byte inside the INI
>> file. The issues APC is having with certain code is not specific to
>> APC, and does happen with other open source caches. Perhaps we need to
>
> We don't discuss putting other OSS (or non-OSS for that matter :) caches in
> any PHP build, enabled by default, do we? That's the point.
> And really, enabling extension - either in source build or in binary build -
> is not that hard. If they are able to write PHP, they should be able to
> remove ; before extension= or write --enable-apc.
>
>> examine the validity of that code, or simply not cache the code that's
>> affected.
>
> I'd rather not make such kludges, especially if we talk about main PHP
> source. It's not a good road to take.
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
>