Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128785
Precedence: list
MIME-Version: 1.0
References: <CAMW7n8DGbFnQzjt3s9CcOBwhp+MUOV+K3U=yY=ULOTdUXaOLHQ@mail.gmail.com>
 <CADuktwNP+t-DJbLCsnHHhztZYmOMGYde9rzNm+9B0SUsrNvV-g@mail.gmail.com>
In-Reply-To: <CADuktwNP+t-DJbLCsnHHhztZYmOMGYde9rzNm+9B0SUsrNvV-g@mail.gmail.com>
Date: Mon, 6 Oct 2025 08:34:43 +0300
Message-ID: <CAMW7n8BTb1OHdLsjD+fPyeGOkYSQx-KXMrLnG-4rVUSq2646+Q@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP True Async RFC Stage 4
To: Adam Cable <adamcable@gmail.com>
Cc: php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: edmond.ht@gmail.com (Edmond Dantes)

Hello.

> Just a quick question - other methods that tried to provide async/paralle=
l type functionality previously were only available via the CLI.

TrueAsync itself is integrated into PHP in such a way that it is
always active. The scenario you described is technically possible (Of
course, this can also be useful for sending telemetry in a way that
doesn=E2=80=99t interfere with request processing.), but it=E2=80=99s not p=
articularly
relevant in the context of modern development.

Why?

Because client requests are usually processed sequentially, step by
step. Parallel tasks are rare. Therefore, from the server=E2=80=99s
perspective, the main benefit of concurrency is the ability to handle
multiple requests within a single process. The same thing that Swoole,
AMPHP, and other modern backend solutions do.

And this is one of the reasons why FPM is morally outdated and
therefore not used in stateful backends. That=E2=80=99s why you encounter C=
LI
so often.