Re: [RFC] Extension Prepend Files
| From: | Benjamin Eberlei | Date: | Tue, 06 Jan 2015 11:37:50 +0000 |
| Subject: | Re: [RFC] Extension Prepend Files | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-80230@lists.php.net to get a copy of this message | ||
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
>