Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122081
MIME-Version: 1.0
References: <CADU7aovcatZ++PSg0Pt0-kXJH9Oe09N0jy5uXEoBYoRv6GeUwQ@mail.gmail.com>
 <5060b986-2e5a-46e4-9c83-763e5b155e83@gmail.com> <CADU7aoutXwr2puZnzMJk+iNfxf-xE-2DKviSTHLK+TR3xpzsQA@mail.gmail.com>
 <6f7815b9-80cc-4e08-819a-49dca090116f@gmail.com> <CAPzBOBMzL78Fxb+sDTyfCoR0psKzkp8o50+RwQ2Y3Sz+K+7jUQ@mail.gmail.com>
 <7F63D301-1A46-49AA-9140-F64543E902C5@gmail.com> <8fb6672c-06e9-4f74-b2f2-cd1a265c75a5@app.fastmail.com>
 <96C28696-7C58-4018-84EB-69CF4189649B@gmail.com> <CADU7aotEhGSVUXYu_9Uhge-VA_AgUrLUPd7Ud+yq=9khh1bosw@mail.gmail.com>
 <881CFFCD-220F-4A58-B5B9-C1FFFCE5E278@gmail.com> <CAEZPtU69HWEPRb=L=oBNYL7+xdGM8xQqgB6KO0sDP6-iMuK0ug@mail.gmail.com>
 <2462CAA8-3E66-4DAD-8489-77E035708087@gmail.com>
In-Reply-To: <2462CAA8-3E66-4DAD-8489-77E035708087@gmail.com>
Date: Mon, 1 Jan 2024 18:40:17 +0100
Message-ID: <CAPzBOBPouG5Fo9aEzcMGZq_Y60EeXxqyP96YPaVrUX3eSJF7wA@mail.gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Cc: Pierre Joye <pierre.php@gmail.com>, php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] RFC proposal: worker mode primitives for SAPIs
From: landers.robert@gmail.com (Robert Landers)

On Mon, Jan 1, 2024 at 12:18=E2=80=AFPM Rowan Tommins <rowan.collins@gmail.=
com> wrote:
>
> On 31 December 2023 16:31:31 GMT, Pierre Joye <pierre.php@gmail.com> wrot=
e:
>
> >php handles this in threadsafe mode
>
> Depending on your exact definition of "php", this is either irrelevant or=
 just plain wrong.
>
> If you mean "the HTTP SAPIs shipped with official builds of PHP", then it=
's true, none handle multiple concurrent requests in a single thread using =
async I/O. But none handle multiple consecutive requests in a single thread=
 using a "worker mode" either, which is the whole point of this conversatio=
n.
>
> If you mean for "php" to include third party HTTP handlers such as Franke=
nPHP, then it also includes Swoole, which is what I was describing. Please =
someone correct me if I'm wrong, but I understand ReactPHP and AMPHP also i=
nclude HTTP servers using the same principle.
>
> So, to reiterate my point once more: implementations of PHP using async c=
oncurrency are out there already in production use. If we're attempting to =
standardise a new API for worker modes (i.e. HTTP servers which are no long=
er "shared nothing"), choosing one which can be used by consecutive worker =
modes (FrankenPHP , RoadRunner) but not concurrent ones (Swoole, ReactPHP, =
AMPHP) feels like a big missed opportunity.
>
> Regards,
>
> --
> Rowan Tommins
> [IMSoP]
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>

Hey Rowan,

I'm not sure concurrent servers would even be able to be in scope if
we wanted them to be? PHP doesn't have an "event-loop", concurrent
i/o, or any building blocks needed to serve concurrent requests. It's
been made possible through extensions and libraries that aren't
maintained by PHP, so I'm not sure how we'd support them directly
without those other basic functionalities. If we directly wanted to
support concurrent servers, I think there is probably a lot of work to
do at a very low level before we could realistically include them in
this part of the conversation.




Robert Landers
Software Engineer
Utrecht NL