Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67384 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 65225 invoked from network); 10 May 2013 02:31:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 May 2013 02:31:26 -0000 Authentication-Results: pb1.pair.com header.from=laruence@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=laruence@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.181 as permitted sender) X-PHP-List-Original-Sender: laruence@gmail.com X-Host-Fingerprint: 209.85.217.181 mail-lb0-f181.google.com Received: from [209.85.217.181] ([209.85.217.181:41968] helo=mail-lb0-f181.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3A/B1-53423-AFB5C815 for ; Thu, 09 May 2013 22:31:23 -0400 Received: by mail-lb0-f181.google.com with SMTP id w10so3723340lbi.40 for ; Thu, 09 May 2013 19:31:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=hFuS75hTHYJ3inoyebxFM2FQXinA3Av0vhJk3LiXnUI=; b=0v/bUEKDMcVXzgIZHGaI975HjJjEntAAW9QHos3wCiz2oPA47jrQG22gpGFSMqXRxh epOlfnQEWRjxdrUuGOiF/groJ7cRYSntecrwbqucF4r6Aj30C2A5cwyeBg0oRvXXGVtp bv+rpJAHB1VRkb/CBeyrM/61kGNdVsWYFg2Ha8rpQMGJ6SoFfHVOYJHMICADThWczwON nYzpuivYrd2sc1Z9Q1wJi44ZSr9NpamO5m+jPTIX5Kl5tWNikkemhRrnhHdsRo0rvBqa GLxEBqrjo0RWhAhMgeINei7fxK1q75bEvI+MNYa9Rb8VwsVm2o/He0KjOgPx7+Pfwec0 naXg== X-Received: by 10.152.1.232 with SMTP id 8mr6714338lap.33.1368153079376; Thu, 09 May 2013 19:31:19 -0700 (PDT) MIME-Version: 1.0 Sender: laruence@gmail.com Received: by 10.114.11.129 with HTTP; Thu, 9 May 2013 19:30:59 -0700 (PDT) In-Reply-To: References: Date: Fri, 10 May 2013 10:30:59 +0800 X-Google-Sender-Auth: _OorW9HKMnoPWgVXA-pfTDDdoeE Message-ID: To: Pierre Schmitz Cc: PHP Internals Content-Type: multipart/alternative; boundary=089e011839be4b71a104dc53f61e Subject: Re: [PHP-DEV] PHP 5.5 and APC user cache upgrade path From: laruence@php.net (Laruence) --089e011839be4b71a104dc53f61e Content-Type: text/plain; charset=UTF-8 Hey: besides APCu, you can also have a try with : https://github.com/laruence/yac :) thanks On Thu, May 9, 2013 at 8:02 PM, Pierre Schmitz 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 > > -- Laruence Xinchen Hui http://www.laruence.com/ --089e011839be4b71a104dc53f61e--