Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89685
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <565F6647.1080602@php.net>
References: <565F6647.1080602@php.net>
Date: Mon, 7 Dec 2015 11:00:03 +0700
Message-ID: <CAEZPtU5pg=f=L+oQRvb1N-Lyb+0AmKfZRS5ax62de1F7zf9YWQ@mail.gmail.com>
To: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= <francois@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11405f046b0c8a052646e4d8
Subject: Re: [PHP-DEV] PCS (PHP Code Service)
From: pierre.php@gmail.com (Pierre Joye)

--001a11405f046b0c8a052646e4d8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Fran=C3=A7ois,

On Dec 3, 2015 4:44 AM, "Fran=C3=A7ois Laupretre" <francois@php.net> wrote:
>
> Hi,
>
> I'd like to open a discussion about a new PHP extension named PCS.
>
> PCS stands for 'PHP Code Service' and it is (yet) another way to mix C
and PHP code in extensions.
>
> Some months ago (January 2015), we had come to the conclusion that two
issues needed to be solved : allow the PHP code to be opcache-d, and avoid
loading every script at RINIT. PCS proposes a solution for both via a
stream wrapper and an autoloader.
>
> During this discussion, it also became clear that two different sources
of PHP scripts should be supported : some want to embed and distribute
scripts in the compiled module, and others want to store them in a separate
location on the host. So, PCS supports both architectures or even a mix of
both.
>
> The documentation is available at http://pcs.tekwire.net :
>
> - the 'Introduction' document details the pros and cons of the different
approaches,
> - and a tutorial describes in details how to embed the MongoDB PHP
library in the MongoDB C extension.
>
> If this discussion results in a positive consensus, and because PCS may
potentially be used to rewrite parts of core extensions from C to PHP, I'll
write an RFC proposing to include it in the 7.1 core distrib.
>
> Note : don't use the 'pecl install' command to get PCS, download from
PECL. I still need to find a workaround for the 'pecl' command bug.

Very nice work! :)

For the core and to begin with, I would however prefer a very focused
feature, to allow to bundle php code in an extension binary and make it
available to userland, including opcache support (what is missing now). Any
other features, while being useful in some situations, will make it harder
to maintain and may be the next phar. Also many of these features could
live well in an external extensions keeping the core part simple.

Cheers,
Pierre

--001a11405f046b0c8a052646e4d8--