Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122121
MIME-Version: 1.0
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>
 <99C434B3-3953-4E90-8DEA-94237332219D@gmail.com> <CAPzBOBPRGBOp36sgJf0BoTaZjbi3HT7TW-9eZpS7h9w+OORfyA@mail.gmail.com>
In-Reply-To: <CAPzBOBPRGBOp36sgJf0BoTaZjbi3HT7TW-9eZpS7h9w+OORfyA@mail.gmail.com>
Date: Fri, 5 Jan 2024 13:40:15 +0100
Message-ID: <CABdc3Wp9fw_4bci6XSqFeWMNt4Z6aY0M+Vs8HhrgmWs5SMc=Mw@mail.gmail.com>
To: Robert Landers <landers.robert@gmail.com>
Cc: Rowan Tommins <rowan.collins@gmail.com>, internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000202760060e322720"
Subject: Re: [PHP-DEV] RFC proposal: worker mode primitives for SAPIs
From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Marcin_Brzuchalski?=)

--000000000000202760060e322720
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

pt., 5 sty 2024 o 13:19 Robert Landers <landers.robert@gmail.com>
napisa=C5=82(a):

> On Fri, Jan 5, 2024 at 11:59=E2=80=AFAM Rowan Tommins <rowan.collins@gmai=
l.com>
> wrote:
>
> > > Globals is how this works (atm)
> >
> > It's how it works for native SAPIs. It's not, as far as I know, how any
> worker system other than FrankenPHP has implemented its API. Every other
> implementation I've seen, whether async or not, passes in some form of
> request data to the callback, with the exception of RoadRunner, which giv=
es
> the data as a return value from a "get next request" function.
>
> Nearly every library in existence knows how to use these globals
> (including 30 years old legacy code). There are also the unwieldy PSR
> request/response containers for which there are dozens (if not
> hundreds) of implementations. It would be fantastic if there were
> already an extension-based implementation that could be adopted into
> php-src; though I feel like that is a separate conversation.
>

There are indeed dozens of libraries already working with PSR nicely but
IMHO
the API should provide all the necessary information in a way that allows
the construction of such objects,
but suggesting PSR with request/response objects will limit the
capabilities of worker mode API
to handle pure HTTP protocol only.

What I'd like to say is that I believe for the initial proposal of any
eventual worker mode API
with the PSR with request/response objects should not be considered at all.

Cheers

--000000000000202760060e322720--