Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129944
Precedence: list
MIME-Version: 1.0
References: <CAMW7n8B9XHzF5ND21-hNYtw26EnE+0b+W0Nv=wb_ayMmu4CbKw@mail.gmail.com>
 <CAMW7n8C1m08+pKKYBGkMnNZmGmu-_kkxS-r_SCuRupBY+RHe5A@mail.gmail.com>
 <CANCsWvfXWDjdmKFFQvV0Ger6yNVSfOhQqnbyTr7bEQHSjmXyLg@mail.gmail.com>
 <79CDB2CC-E397-436E-B5A2-10DA1E451A97@rwec.co.uk> <CAMW7n8CvVD4zNGELeYV3MWP2z0bRgF6jA0WWnafCkNE8-Ka4BQ@mail.gmail.com>
In-Reply-To: <CAMW7n8CvVD4zNGELeYV3MWP2z0bRgF6jA0WWnafCkNE8-Ka4BQ@mail.gmail.com>
Date: Tue, 27 Jan 2026 20:17:42 +0200
Message-ID: <CAMW7n8BBykb08BoHphvoLa0cPts=obs9=u_SS-9dCwoYmc=HVQ@mail.gmail.com>
Subject: Re: [PHP-DEV] Re: [RFC] True Async RFC 1.7
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.

At the moment, this RFC has no chance of being accepted. And it=E2=80=99s n=
ot
about the text itself. Therefore, a different approach is needed.

So:

1. The vote scheduled for **February 1 is canceled**.
2. Daniil Gentili is officially joining TrueAsync and will help with
the RFC discussion.
3. Aaron Piotrowski has also received an invitation.
4. In addition to the features described in the RFC, other
experimental capabilities will also be developed.

This also means that from now on, this RFC will be the result of the
work of several people.

If anyone else would like to join, please let me know.
I also officially invite maintainers of frameworks and web servers to
take part in testing, in order to adapt them for async operation.
It would be great if someone built WebSocket integration. The PHP
community has been waiting for this for a long time for about 15 years
already.

As for what happens next, I think Daniil Gentili will explain it himself.