Re: Is the fix for #61238 in PHP 5.4.4 & pecl yet?
| From: | Tom Boutell | Date: | Tue, 03 Jul 2012 15:53:36 +0000 |
| Subject: | Re: Is the fix for #61238 in PHP 5.4.4 & pecl yet? | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-61091@lists.php.net to get a copy of this message | ||
The ability to store your own data in the APC cache is a feature that
does get used a lot in the Symfony framework world because of the
availability of the sfAPCCache and whatever its Symfony 2 equivalent
is. It's popular with folks who haven't felt the need to set up Redis
or some other external cache yet. I'm not sure whether this is
something you consider a "legacy feature."
On Tue, Jul 3, 2012 at 11:17 AM, Pierre Joye <pierre.php@gmail.com> wrote:
> hi,
>
> On Tue, Jul 3, 2012 at 5:12 PM, Arvids Godjuks <arvids.godjuks@gmail.com> wrote:
>> There are alternative opcode cachers besides APC. For example xcache, for
>> me, just works when APC is still catching up.
>> I remember someone writing about APC that it is overly compex internally
>> and due to that hard to keep up with the changes in the PHP, maybe that is
>> not the case now.
>
> It is still the case.
>
> I for one would like to kill all the legacy features or too specific
> features which are really unusable by any common developers.
>
> Other developers may disagree but it makes very hard to maintain APC.
>
> Cheers,
>
>> 2012/7/3 Tom Boutell <tom@punkave.com>
>>
>>> Given the impracticality of using PHP without APC, it would be nice if
>>> it were part of the main "if these fail, it's not ready" test suite.
>>> But I suppose that's just administering beatings until morale improves
>>> (:
>
>
>
> --
> Pierre
>
> @pierrejoye | http://blog.thepimp.net |
> http://www.libgd.org
--
Tom Boutell
P'unk Avenue
215 755 1330
punkave.com
window.punkave.com