Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128863
Precedence: list
MIME-Version: 1.0
References: <CAMW7n8DGbFnQzjt3s9CcOBwhp+MUOV+K3U=yY=ULOTdUXaOLHQ@mail.gmail.com>
In-Reply-To: <CAMW7n8DGbFnQzjt3s9CcOBwhp+MUOV+K3U=yY=ULOTdUXaOLHQ@mail.gmail.com>
Date: Sun, 19 Oct 2025 08:03:08 +0300
Message-ID: <CAMW7n8Dcp4VGmR-cL4AO7s5cvbHLYHxXJg8LdpqAas7Z5KUEiQ@mail.gmail.com>
Subject: [PHP-DEV] Re: PHP True Async RFC Stage 4
To: 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 everyone,

Tomorrow marks two weeks since the RFC was published, which means
that, formally, it is now eligible to be submitted for voting.

Allow me to briefly summarize the current state of the project:

1. The implementation has been delivered both as **core changes to
PHP** and as a **separate extension**.
2. **More than 50 PHP functions** have been adapted to work in
**non-blocking mode**, all of which are fully **covered by tests**.
3. There is a working **integration example with a web server** using
the model _=E2=80=9Creact-process + embedded PHP process=E2=80=9D_.
4. The project is currently in an **Alpha+ stage**, and is **available
for testing and experimentation**.
5. The **RFC v3 has been implemented almost entirely**, and **RFC v4
is fully covered**.
6. The **second version of the PHP Stream integration** demonstrates
**strong I/O performance** in **web server scenarios**.
7. The code introduces asynchrony into all stages of PHP execution,
including ensuring correct GC operation. It successfully passes the
standard PHP test suite.
8. Supports both ZTS and non-ZTS builds.
9. Separate testing was performed with XDebug (with a small patch applied).

At this stage, all technical objectives of the project have been achieved 1=
00%.
To emphasize: the project is not yet production-ready, but it has
fully achieved its demonstration goals.

Around this time, the project turned one year old.

**RFC**

1. A high-level API for PHP land has been developed, based on the
experience of other programming languages.
2. Known development pitfalls have been taken into account, and
fault-tolerant solutions have been incorporated.

At this point, all RFC objectives have been achieved.

My special thanks go to Roman Pronskiy, Jakub Zelenka, Arnaud Le
Blanc, Valentin Udaltsov as well as to everyone who supported the
project in various ways.

Dear PHP community, we are now at a decision point: what should be done nex=
t?

I am obliged to draw the attention of the PHP community to the fact
that the Swow project has existed for several years. Unlike TrueAsync,
it is more **mature**, and its author Twose has previously expressed
an intention to integrate it into the core.
This RFC can be used as a foundation regardless of the implementation.
So I believe that Twose=E2=80=99s opinion is important and should be taken
into consideration.

I recommend voting for the TrueAsync RFC with the status of =E2=80=9Cexperi=
mental=E2=80=9D.
Although this status is not formally defined in PHP rules, it would
allow framework authors, library developers, and other maintainers to
treat this RFC and its implementation as something expected to be
adopted in the future.
Without this step, further development makes little sense.
There is no point in creating an equivalent of Swoole or Swow. These
projects already exist, are excellently built, and fulfill their
purpose.

**For the moderators**

It is possible that voting on this RFC may not make sense. If that is
the case, please state so within the next 2-3 days.
This would be a rational and respectful approach toward the
participants of the vote.

Thank you all, and best of luck.