Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61096
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAORXhGLH6LhL9_x7UwH5V715Qn6aZF+4v+FbW53Ars9=B0pPiQ@mail.gmail.com>
References: <CAORXhGJ0NgxXJFoa6YswV5-EsRXqSDNKXTvhdL=7q=Knygr0sQ@mail.gmail.com>
	<4FF2FFBF.8050301@lerdorf.com>
	<CAORXhGKH8u7funSGC-wBtPNe2YMAMNL+0iVrK3m_-NCJ8Ld50g@mail.gmail.com>
	<CAL0xaBHk=x8uaYCcm7eJwJci-iMBND1caFENairj7zaS3EsD1A@mail.gmail.com>
	<CAEZPtU7hHTJrb78ACufYLTnB1y_7JfgAhdECjiwxM-cas4Ardw@mail.gmail.com>
	<CAORXhGLH6LhL9_x7UwH5V715Qn6aZF+4v+FbW53Ars9=B0pPiQ@mail.gmail.com>
Date: Tue, 3 Jul 2012 19:54:51 +0300
Message-ID: <CAL0xaBGrcDyzgxVq9LCBjWdzuH3FQJJrAtGsYWvnu0oTshK6Uw@mail.gmail.com>
To: Tom Boutell <tom@punkave.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=20cf30363963e8af3804c3efc59c
Subject: Re: [PHP-DEV] Is the fix for #61238 in PHP 5.4.4 & pecl yet?
From: arvids.godjuks@gmail.com (Arvids Godjuks)

--20cf30363963e8af3804c3efc59c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Just to be clear - all 3 major opcode cachers i know (zend optimizer
excluded - have no idea what he has) have that shared memory cache with
almost identical API. Some have extended functionality (xcache has
xcache_isset(), haven't seen that in others, but have to confess i haven't
been looking for some time now), so they are easily swappable.
03.07.2012 15:54 =D0=BF=D0=BE=D0=BB=D1=8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=
=B5=D0=BB=D1=8C "Tom Boutell" <tom@punkave.com> =D0=BD=D0=B0=D0=BF=D0=B8=D1=
=81=D0=B0=D0=BB:

> 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.co=
m>
> 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 internal=
ly
> >> and due to that hard to keep up with the changes in the PHP, maybe tha=
t
> 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 i=
f
> >>> 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 improve=
s
> >>> (:
> >
> >
> >
> > --
> > Pierre
> >
> > @pierrejoye | http://blog.thepimp.net | http://www.libgd.org
>
>
>
> --
> Tom Boutell
> P'unk Avenue
> 215 755 1330
> punkave.com
> window.punkave.com
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--20cf30363963e8af3804c3efc59c--