Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66605
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.49 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CADegSEbVU9MxX8e71tvCRLKN4SMLfcX+m=enKo13Wn=05QTEjA@mail.gmail.com>
References: <CADegSEbVU9MxX8e71tvCRLKN4SMLfcX+m=enKo13Wn=05QTEjA@mail.gmail.com>
Date: Thu, 14 Mar 2013 08:08:23 +0100
Message-ID: <CADegSEYmmQRvnEaJ=PMjEgPiLVWjNb0EGV6FxYopYBXuMchiZA@mail.gmail.com>
To: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0160c18c0f4cec04d7dd323b
Subject: Re: feature request : easy shared memory
From: rene7705@gmail.com (rene7705)

--089e0160c18c0f4cec04d7dd323b
Content-Type: text/plain; charset=ISO-8859-1

oh, if no PHP threads/processes are active, all sharedmem's would still be
allocated by the PHP OS-level process itself, of course, to prevent any
overhead as new PHP calls are made that access this sharedmem.


On Thu, Mar 14, 2013 at 8:05 AM, rene7705 <rene7705@gmail.com> wrote:

> Hi.
>
> I'd like to build a replacement for SQL (yes, talk about an ambitious
> project! ;), because the constant transferal of data in and out of SQL from
> Javascript (where everything might as well be object-oriented and
> hierarchial) is a pain in the neck.
>
> But in order to do so, I'd very much like PHP (the server still controls
> the data after all) to support shared memory efficiently.
>
> Something like
>
> sharedmem $bigNestedArray; // $bigNestedArray would be shared accross the
> entire server and all CPUs on it.
>
> as you now have
>
> global $bigNestedArray;
>
> would be ideal.
>
> I bet this would be useful for a host of other applications as well, and
> fairly easy to implement.
>
> I'm an application programmer by trade, or I would hack this in myself.
>
> I'd much rather see the PHP development team develop this in properly. I
> don't think it would require much time, as OS-level shared memory has been
> easy to implement since the 1990s.
>
> Please put this on the agenda, and get back to us in this thread as to
> when this will be available.
>

--089e0160c18c0f4cec04d7dd323b--