Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92732
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.54 as permitted sender)
To: internals@lists.php.net
References: <CALW=WECkP4D7QHbAt9LCE0DT=40qyYk5iEspUSpjG4MUKTi6Rg@mail.gmail.com>
Message-ID: <571E2B75.6000909@gmail.com>
Date: Mon, 25 Apr 2016 15:36:37 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CALW=WECkP4D7QHbAt9LCE0DT=40qyYk5iEspUSpjG4MUKTi6Rg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Opcache::get($key), set($key, $value) to shared memory,
 is planned in PHP 7.1?
From: rowan.collins@gmail.com (Rowan Collins)

S.A.N wrote on 25/04/2016 15:09:
> In userland  lacks the ability to store data in the shared memory
> modules, do not use pecl modules, it would be very nice to have a
> function:
>
> opcache_get($key);
> opcache_set($key, $value);
>
> Is planned in PHP 7.1?
>

This was identified as a difference between APC and OpCache when the 
latter was added to core several releases ago, and that's exactly why 
APCu exists: http://php.net/apcu

There's not really a huge connection between opcode caching and 
optimization (OpCache) and shared memory data caches (APCu, memcached, 
etc), so I don't think there's any particular logic to calling such 
functions "opcache".

So I guess the question becomes: "should APCu be made part of core?" I'm 
not aware of anyone having proposed that, so don't know if there are 
strong feelings for or against such a thing.

Regards,
-- 
Rowan Collins
[IMSoP]