Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104789
MIME-Version: 1.0
Date: Mon, 18 Mar 2019 21:15:56 +0100
Message-ID: <CADqTB_i7zXnAqU1w1kuMStz2sHdpMcYTGGDJfwZeG0-+YFUckQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000f9a9460584640e60"
Subject: unload/reload classes?
From: rasmus@mindplay.dk (Rasmus Schultz)

--000000000000f9a9460584640e60
Content-Type: text/plain; charset="UTF-8"

Hello internals,

How hard would be to add an unload (or reload) feature for
classes/interfaces?

I'm wondering with regards to running PHP as a deamon (with Swoole or
ReactPHP, etc.) could it be made possible to hot-reload e.g. for
controllers and view-models?

Of course, the other option is to launch worker sub-processes under some
sort of host process, and then restart the workers after a change - this
adds communication overhead between the host/worker processes though, and a
layer of complexity.

Another option is if a reverse proxy (NGINX maybe) could restart the actual
application daemon, but that means you have a dependency on a specific
reverse proxy.

So I know there are other options, but I'm looking for the simplest and
cleanest way to do this, and I'd prefer to stay within the language.

Other dynamic languages (where daemonizing is "normal", like Ruby, JS and
Python) have this feature and it is often used to hot-reload
controllers/views in web-apps.

Any thoughts?

--000000000000f9a9460584640e60--