Hello, On Tue, Dec 26, 2023, 1:56 AM Jordan LeDoux <jordan.led...@gmail.com> wrote:
> > So you want to introduce a SAPI that doesn't work with any of the existing > HTTP solutions people use that only supports HTTP requests? Or am I > misunderstanding something? > > This sounds a bit like you want to merge in a tool that is designed for > your personal product directly into core. FrankenPHP may be incredible and > awesome, but the world runs on Apache and Nginx for HTTP requests. The world was running on cgi when php was created and a few years after. Then the world was running on threads/apache. Then it ran in fcgi and finally fcgi fpm for the last few years. Other languages support this since quite some time. Projects like reactphp, swoole and the likes provide userland versions of it and the benefits are clear. They even worked together recently to get a common core. Many (large) projects out there already support FrankenPHP, the needs are there. FrankenPhp and a worker mode go beyond the classical php usages we had. Desktop applications or IoT are getting more common (see laravel's nativephp f.e.). I have done something similar for one of our products using embedded sapi but how it is done using frankenphp would be an order of magnitude better. Having the complex parts in the core us a good start to experiment, adapt. Later a core sapi may be added, we cannot know without trying and let the community uses it. best, Pierre
