Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128782
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, 5 Oct 2025 20:23:22 +0100
Message-ID: <CADuktwNP+t-DJbLCsnHHhztZYmOMGYde9rzNm+9B0SUsrNvV-g@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP True Async RFC Stage 4
To: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000003ebfc106406e4589"
From: adamcable@gmail.com (Adam Cable)

--0000000000003ebfc106406e4589
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sun, Oct 5, 2025 at 7:51=E2=80=AFAM Edmond Dantes <edmond.ht@gmail.com> =
wrote:

> Good day, everyone. I hope you're doing well.
>
> 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 we=
ll.
> Many thanks to everyone for your input!
>
> https://wiki.php.net/rfc/true_async
>
> **What has changed in this version?**
>
> The RFC has been significantly simplified:
>
> 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 shutdown_=
function.
> 3. Added Memory Management and Garbage Collection section
>
> 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.
>
> During this time, I managed to refactor and optimize the TrueAsync
> code, which showed promising performance results in I/O scenarios.
>
> 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-async=
-php
>
> During this time, the project has come very close to beta status.
>
> Once again, I want to thank everyone who supported me during difficult
> times, offered advice, and helped develop this project.
>
> Given the maturity of both the code and the RFC, this time I hope to
> proceed with a vote.
>
> Wishing you all a great day, and thank you for your feedback!
>

Hi, I am so looking forward to this capability!

Just a quick question - other methods that tried to provide async/parallel
type functionality previously were only available via the CLI.

I can see a big opportunity for people running websites with Apache +
PHP-FPM where on each page request you do stuff like:

Call API 1 (e.g. external auth component)
Call API 2 (e.g. product catalogue)
Call API 3 (e.g. setup payment processor)

Am hoping that you could put these three calls within a Scope and therefore
have all three calls run at the same time, and only have to wait as long as
the slowest API, rather than the combination of all 3 response times.

I didn't see anything in the RFC about this, so just wanted to check.

Thanks,
Adam

--0000000000003ebfc106406e4589
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g=
mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Oct 5, =
2025 at 7:51=E2=80=AFAM Edmond Dantes &lt;<a href=3D"mailto:edmond.ht@gmail=
.com">edmond.ht@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex">Good day, everyone. I hope you&#39;re doing well.<=
br>
<br>
I=E2=80=99m happy to present the fourth version of the RFC. It wasn=E2=80=
=99t just me<br>
who worked on it =E2=80=94 members of the PHP community contributed as well=
.<br>
Many thanks to everyone for your input!<br>
<br>
<a href=3D"https://wiki.php.net/rfc/true_async" rel=3D"noreferrer" target=
=3D"_blank">https://wiki.php.net/rfc/true_async</a><br>
<br>
**What has changed in this version?**<br>
<br>
The RFC has been significantly simplified:<br>
<br>
1. Components (such as TaskGroup) that can be discussed in separate<br>
RFCs have been removed from the current one.<br>
2. Coroutines can now be created anywhere =E2=80=94 even inside shutdown_fu=
nction.<br>
3. Added Memory Management and Garbage Collection section<br>
<br>
Although work on the previous API RFC was interrupted and we weren=E2=80=99=
t<br>
able to include it in PHP 8.5, it still provided valuable feedback on<br>
the Async API code.<br>
<br>
During this time, I managed to refactor and optimize the TrueAsync<br>
code, which showed promising performance results in I/O scenarios.<br>
<br>
A test integration between **NGINX UNIT** and the **TrueAsync API**<br>
was implemented to evaluate the possibility of using PHP as an<br>
asynchronous backend for a web server:<br>
<a href=3D"https://github.com/EdmondDantes/nginx-unit/tree/true-async/src/t=
rue-async-php" rel=3D"noreferrer" target=3D"_blank">https://github.com/Edmo=
ndDantes/nginx-unit/tree/true-async/src/true-async-php</a><br>
<br>
During this time, the project has come very close to beta status.<br>
<br>
Once again, I want to thank everyone who supported me during difficult<br>
times, offered advice, and helped develop this project.<br>
<br>
Given the maturity of both the code and the RFC, this time I hope to<br>
proceed with a vote.<br>
<br>
Wishing you all a great day, and thank you for your feedback!<br></blockquo=
te><div><br></div><div dir=3D"auto">Hi, I am so looking forward to this cap=
ability!</div><div dir=3D"auto"><br></div><div dir=3D"auto">Just a quick qu=
estion - other methods that tried to provide async/parallel type functional=
ity previously were only available via the CLI.</div><div dir=3D"auto"><br>=
</div><div dir=3D"auto">I can see a big opportunity for people running webs=
ites with Apache + PHP-FPM where on each page request you do stuff like:</d=
iv><div dir=3D"auto"><br></div><div dir=3D"auto">Call API 1 (e.g. external =
auth component)</div><div dir=3D"auto">Call API 2 (e.g. product catalogue)<=
/div><div dir=3D"auto">Call API 3 (e.g. setup payment processor)</div><div =
dir=3D"auto"><br></div><div dir=3D"auto">Am hoping that you could put these=
 three calls within a Scope and therefore have all three calls run at the s=
ame time, and only have to wait as long as the slowest API, rather than the=
 combination of all 3 response times.</div><div dir=3D"auto"><br></div><div=
 dir=3D"auto">I didn&#39;t see anything in the RFC about this, so just want=
ed to check.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Thanks,</di=
v><div>Adam=C2=A0</div></div></div>

--0000000000003ebfc106406e4589--