Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128841
Feedback-ID: ifab94697:Fastmail
Precedence: list
MIME-Version: 1.0
Date: Wed, 15 Oct 2025 08:44:23 +0200
To: internals@lists.php.net
Message-ID: <bcd8253c-04f3-4046-b51f-2e387e215f6d@app.fastmail.com>
In-Reply-To: 
 <CAMW7n8DGbFnQzjt3s9CcOBwhp+MUOV+K3U=yY=ULOTdUXaOLHQ@mail.gmail.com>
References: 
 <CAMW7n8DGbFnQzjt3s9CcOBwhp+MUOV+K3U=yY=ULOTdUXaOLHQ@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP True Async RFC Stage 4
Content-Type: multipart/alternative;
 boundary=96d42f32ce7c4830b8ae965a532d61fc
From: rob@bottled.codes ("Rob Landers")

--96d42f32ce7c4830b8ae965a532d61fc
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On Sun, Oct 5, 2025, at 07:23, Edmond Dantes wrote:
> Good day, everyone. I hope you're doing well.
>=20
> I=E2=80=99m happy to present the fourth version of the RFC. It wasn=E2=
=80=99t just me
> who worked on it =E2=80=94 members of the PHP community contributed as=
 well.
> Many thanks to everyone for your input!
>=20
> https://wiki.php.net/rfc/true_async
>=20
> **What has changed in this version?**
>=20
> The RFC has been significantly simplified:
>=20
> 1. Components (such as TaskGroup) that can be discussed in separate
> RFCs have been removed from the current one.
> 2. Coroutines can now be created anywhere =E2=80=94 even inside shutdo=
wn_function.
> 3. Added Memory Management and Garbage Collection section
>=20
> Although work on the previous API RFC was interrupted and we weren=E2=80=
=99t
> able to include it in PHP 8.5, it still provided valuable feedback on
> the Async API code.
>=20
> During this time, I managed to refactor and optimize the TrueAsync
> code, which showed promising performance results in I/O scenarios.
>=20
> A test integration between **NGINX UNIT** and the **TrueAsync API**
> was implemented to evaluate the possibility of using PHP as an
> asynchronous backend for a web server:
> https://github.com/EdmondDantes/nginx-unit/tree/true-async/src/true-as=
ync-php
>=20
> During this time, the project has come very close to beta status.
>=20
> Once again, I want to thank everyone who supported me during difficult
> times, offered advice, and helped develop this project.
>=20
> Given the maturity of both the code and the RFC, this time I hope to
> proceed with a vote.
>=20
> Wishing you all a great day, and thank you for your feedback!
>=20

Hello,

I=E2=80=99m not even half way done with a list of comments and questions=
, but I have one that continues to bother me while reading, so I figure =
I will just ask it.

Why doesn=E2=80=99t scope implement Awaitable?

=E2=80=94 Rob
--96d42f32ce7c4830b8ae965a532d61fc
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title></head><body><div><br></div><d=
iv><br></div><div>On Sun, Oct 5, 2025, at 07:23, Edmond Dantes wrote:</d=
iv><blockquote type=3D"cite" id=3D"qt" style=3D""><div>Good day, everyon=
e. I hope you're doing well.</div><div><br></div><div>I=E2=80=99m happy =
to present the fourth version of the RFC. It wasn=E2=80=99t just me</div=
><div>who worked on it =E2=80=94 members of the PHP community contribute=
d as well.</div><div>Many thanks to everyone for your input!</div><div><=
br></div><div><a href=3D"https://wiki.php.net/rfc/true_async">https://wi=
ki.php.net/rfc/true_async</a></div><div><br></div><div>**What has change=
d in this version?**</div><div><br></div><div>The RFC has been significa=
ntly simplified:</div><div><br></div><div>1. Components (such as TaskGro=
up) that can be discussed in separate</div><div>RFCs have been removed f=
rom the current one.</div><div>2. Coroutines can now be created anywhere=
 =E2=80=94 even inside shutdown_function.</div><div>3. Added Memory Mana=
gement and Garbage Collection section</div><div><br></div><div>Although =
work on the previous API RFC was interrupted and we weren=E2=80=99t</div=
><div>able to include it in PHP 8.5, it still provided valuable feedback=
 on</div><div>the Async API code.</div><div><br></div><div>During this t=
ime, I managed to refactor and optimize the TrueAsync</div><div>code, wh=
ich showed promising performance results in I/O scenarios.</div><div><br=
></div><div>A test integration between **NGINX UNIT** and the **TrueAsyn=
c API**</div><div>was implemented to evaluate the possibility of using P=
HP as an</div><div>asynchronous backend for a web server:</div><div><a h=
ref=3D"https://github.com/EdmondDantes/nginx-unit/tree/true-async/src/tr=
ue-async-php">https://github.com/EdmondDantes/nginx-unit/tree/true-async=
/src/true-async-php</a></div><div><br></div><div>During this time, the p=
roject has come very close to beta status.</div><div><br></div><div>Once=
 again, I want to thank everyone who supported me during difficult</div>=
<div>times, offered advice, and helped develop this project.</div><div><=
br></div><div>Given the maturity of both the code and the RFC, this time=
 I hope to</div><div>proceed with a vote.</div><div><br></div><div>Wishi=
ng you all a great day, and thank you for your feedback!</div><div><br><=
/div></blockquote><div><br></div><div>Hello,</div><div><br></div><div>I=E2=
=80=99m not even half way done with a list of comments and questions, bu=
t I have one that continues to bother me while reading, so I figure I wi=
ll just ask it.</div><div><br></div><div>Why doesn=E2=80=99t scope imple=
ment Awaitable?</div><div><br></div><div id=3D"sig121229152">=E2=80=94 R=
ob</div></body></html>
--96d42f32ce7c4830b8ae965a532d61fc--