Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92762
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pthreads.org from 209.85.161.174 cause and error)
MIME-Version: 1.0
In-Reply-To: <CABBJUpey2movY3doTGRx9KrYs3=Ayagh+3VhmDMgE6L+5SyM=Q@mail.gmail.com>
References: <CALW=WECkP4D7QHbAt9LCE0DT=40qyYk5iEspUSpjG4MUKTi6Rg@mail.gmail.com>
	<CABBJUpey2movY3doTGRx9KrYs3=Ayagh+3VhmDMgE6L+5SyM=Q@mail.gmail.com>
Date: Tue, 26 Apr 2016 08:16:30 +0100
Message-ID: <CAL=_i_k0kwDKfjP+yucxPxFxgxmW2QDnnmY5GTX3U=iX90KDAQ@mail.gmail.com>
To: Xinchen Hui <laruence@php.net>
Cc: "S.A.N" <ua.san.alex@gmail.com>, internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1141e82a7e6b5105315e1257
Subject: Re: [PHP-DEV] Opcache::get($key), set($key, $value) to shared memory,
 is planned in PHP 7.1?
From: pthreads@pthreads.org (Joe Watkins)

--001a1141e82a7e6b5105315e1257
Content-Type: text/plain; charset=UTF-8

Morning,

    To answer the question; No, there is no plan to add that.

    The allocator in opcache is simply not suitable for that kind of use.
We could make it suitable, but the optimal allocator for a user cache, and
the optimal allocator for a code cache, are different things.

    IMO they belong separately.

Cheers
Joe

On Tue, Apr 26, 2016 at 4:17 AM, Xinchen Hui <laruence@php.net> wrote:

> Hey:
>
>
>
> On Mon, Apr 25, 2016 at 10:09 PM, S.A.N <ua.san.alex@gmail.com> wrote:
>
> > 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?
> >
> you could try https://github.com/laruence/yac
>
> it's a  "A fast shared memory user data cache for PHP "
>
> thanks
>
> > --
> > PHP Internals - PHP Runtime Development Mailing List
> > To unsubscribe, visit: http://www.php.net/unsub.php
> >
>
>
>
> --
> Xinchen Hui
> @Laruence
> http://www.laruence.com/
>

--001a1141e82a7e6b5105315e1257--