Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80230
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain beberlei.de from 74.125.82.173 cause and error)
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.11.1501061120440.4080@whisky.home.derickrethans.nl>
References: <CAEPJdu=2oWiSCQOTkO1g5QDs4NrJwd5H14Jks17qrNu7-eQNVg@mail.gmail.com>
	<CAESVnVqAHJujo0anMi7QYhSZeErcfRVAJ=M7oQMG-huk-bxpCg@mail.gmail.com>
	<54AAF98B.4020709@gmail.com>
	<alpine.DEB.2.11.1501061120440.4080@whisky.home.derickrethans.nl>
Date: Tue, 6 Jan 2015 12:37:50 +0100
Message-ID: <CAEPJdu=9+gKY-gWxVBxNzW6sbkqpouwYqgh0JZUeTmU=_0sQ=Q@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: Stanislav Malyshev <smalyshev@gmail.com>, Sara Golemon <pollita@php.net>, 
	PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bb70bb2a22157050bfa3cf2
Subject: Re: [PHP-DEV] [RFC] Extension Prepend Files
From: kontakt@beberlei.de (Benjamin Eberlei)

--047d7bb70bb2a22157050bfa3cf2
Content-Type: text/plain; charset=UTF-8

On Tue, Jan 6, 2015 at 12:24 PM, Derick Rethans <derick@php.net> wrote:

> On Mon, 5 Jan 2015, Stanislav Malyshev wrote:
>
> > > 2) Embedded text sections.  It's possible to place the raw PHP code
> > > into the compiled .so/.dylib/.dll file and fetch it out for
> > > compilation at runtime.  This enables easy bundling of the loaded
> >
> > I guess it is possible, but why - what's wrong with plain old files and
> > phars?
>
> Deployment and installation. Right now, "pecl install extension" doesn't
> really allow you to also install **and** load a PHP script on every
> request. Such a PHP script could define extra classes, that are written
> in PHP - because maintainting them as a C implementation would be way
> more work. Having users install another set of PHP files for every
> project is error prone, and frankly, bad for user experience. I can
> definitely see the use case here, and it's probably something we'd want
> to use for the new MongoDB driver.
>

Yes the deployment aspect isn't discussed in my RFC and that is an
important part.

Frankly most of the ideas presented here are way better than the hack I
have come up with, the question is how to proceed to refine this idea?

The general plan seems to be to have a way to embed PHP code into the
shared object, for example using Autoconf Macros (like the embed extension
mentioned above does)

>
> cheers,
> Derick
>

--047d7bb70bb2a22157050bfa3cf2--