Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122118
Date: Fri, 5 Jan 2024 10:55:02 +0100 (GMT+01:00)
To: internals@lists.php.net
Message-ID: <7c9cc538-c925-4b97-83d7-bc29dc540bd5@gmail.com>
In-Reply-To: <CAPzBOBM0tYMfi5T9K4J3i-1yBg_n=ZyeziGoQBXTvGjXZEOsgg@mail.gmail.com>
References: <CADU7aovcatZ++PSg0Pt0-kXJH9Oe09N0jy5uXEoBYoRv6GeUwQ@mail.gmail.com> <3828a559-5dae-44d1-96ce-dff1a8b07c18@gmail.com> <CAPzBOBOx25-muH8BuMFJAHJp=L8wT_M-W8G-kk6fsPb9Lv_T0A@mail.gmail.com> <DABECB67-A138-4184-8E24-8CC9ED4802C4@gmail.com> <CAPzBOBM0tYMfi5T9K4J3i-1yBg_n=ZyeziGoQBXTvGjXZEOsgg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_4_27601561.1704448503031"
Subject: Re: [PHP-DEV] RFC proposal: worker mode primitives for SAPIs
From: daniil.gentili@gmail.com (Daniil Gentili)

------=_Part_4_27601561.1704448503031
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi,

> But holding up the entire conversation because these things don't even
> exist,

BTW, I'm not asking to wait for the implementation of a native event loop before implementing a worker mode, I'm asking to design the worker mode API in a way that is compatible with an eventual native event loop (that I hope will eventually get merged into php, as the current status quo of blocking STL I/O is definitely not ideal for a programming language in 2024).

Using superglobals for request information is already using a wrong approach in sight of native async, and while technically this is not completely incompatible with fibers, as superglobals can simply be copied immediately as soon a fiber is started, the same cannot be said for php://output and php://input streams, which cannot be copied in any way.

I ask to completely avoid altering superglobals and other global state such as the php://input/output streams, and instead directly pass/return an array/object (it really does not matter to me if it's a PSR-7 RequestInterface or an array containing _GET, _POST, input, output keys, or anything else as long as superglobals and global state is not touched in any way).

Backwards compatibility for code using superglobals is really a non-issue here, as worker mode in itself is already potentially NOT automatically backwards-compatible with legacy code, since applications running in worler mode have to deal with the fact that the global state is not reset at the end of each request.

This in itself is not an issue as mentioned before, thanks to work inside of major PHP frameworks to better support worker mode, I.e. laravel octane, but since the beneficiaries of worker mode will mostly be modern frameworks and most legacy code will already require changes to better support it, using a new API with a standalone request object/array instead of superglobals is not a real issue.

Regards,
Daniil Gentili.

------=_Part_4_27601561.1704448503031--