Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92743
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.195 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <571E2B75.6000909@gmail.com>
References: <CALW=WECkP4D7QHbAt9LCE0DT=40qyYk5iEspUSpjG4MUKTi6Rg@mail.gmail.com>
	<571E2B75.6000909@gmail.com>
Date: Mon, 25 Apr 2016 20:49:13 +0300
Message-ID: <CALW=WEDHi86Z2_x5ggjKOWDjcdaoGfwTktHEx0ATrk-Zut7tZQ@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Opcache::get($key), set($key, $value) to shared memory,
 is planned in PHP 7.1?
From: ua.san.alex@gmail.com ("S.A.N")

2016-04-25 17:36 GMT+03:00 Rowan Collins <rowan.collins@gmail.com>:
> 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.

Yes, there are a lot of libraries to work with shared memory, but why
should they if there OPcache in core PHP?
Functions get, set key values will be useful and in demand.