Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67375
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain dancryer.com does not designate 209.85.214.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <ec8323fa7c2a52a381bf7c18a8242bb2@archlinux.de>
References: <ec8323fa7c2a52a381bf7c18a8242bb2@archlinux.de>
Date: Thu, 9 May 2013 13:22:50 +0100
Message-ID: <CABoMkDYu+gDfF2uEaGtPume2oy8KaoX5hQzuVZT6AVGTdnskOQ@mail.gmail.com>
To: Pierre Schmitz <pierre@archlinux.de>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e013a0768de8a5b04dc481b83
Subject: Re: [PHP-DEV] PHP 5.5 and APC user cache upgrade path
From: dan@dancryer.com (Dan Cryer)

--089e013a0768de8a5b04dc481b83
Content-Type: text/plain; charset=ISO-8859-1

I'm also very keen to understand the expected upgrade path, but from the
perspective of a PHP developer supporting some large bespoke applications
that rely heavily both on opcode caching and the user-caching functionality
of APC.

Is APCu the agreed best path for systems that currently use APC's user
cache?


On Thu, May 9, 2013 at 1:02 PM, Pierre Schmitz <pierre@archlinux.de> wrote:

> Hi,
>
> I am testing PHP 5.5 atm and how we can package it for Arch Linux and
> provide an upgrade path for users. The RC1 looks pretty solid so far.
>
> As the new opcache does not provide a user cache to store custom
> variables, I would be glad if you could clarify what the best migration
> from 5.4 would be.
> * Is APC basically dead and wont support PHP 5.5?
> * Should APC users switch to opcache and APCu? (with APCu replacing the
> APC package)
>
> For PHP application developers:
> * Regarding APCu: it provides the old PHP interface function as well as
> their own apcu_* functions. They are aliases right now. Should
> application developers think about switching to the apcu_-API as new
> features will be available only here?
>
> Bonus question:
> * Right now very similar functionality is provided by APCu, XCache,
> WinCache, YAC etc.. Are there plans to include such functionality inside
> PHP in future to make application developers life a little easier? At
> least a common API would be great. There were several bugs in
> applications as these modules behave a little different regarding return
> values etc..
>
> Greetings,
>
> Pierre
>
> --
> Pierre Schmitz, https://pierre-schmitz.com
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


-- 

*Dan Cryer*

 07590 698944
 dan@dancryer.com
 +Dan <https://plus.google.com/101400775372325517263>
 @dancryer <http://www.twitter.com/dancryer>

--089e013a0768de8a5b04dc481b83--