Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126671
Precedence: bulk
MIME-Version: 1.0
References: <CAMW7n8AJckEDzhGv9BdjNhq8zAdCqb4HsVr56vGi+izw50X6Dg@mail.gmail.com>
 <9964db8c-0ffe-43d5-8246-47fc76b07180@app.fastmail.com> <CAMW7n8CM7oBfXCDsKtV4hTFs40UmLCU3183WjYE2exLNqKDWLQ@mail.gmail.com>
 <78a03dd0-fd4a-4f4a-ad8a-37e5704f06fc@app.fastmail.com> <CAMW7n8C-Z18MKhyDX2+ofg70cRbwWOk=YWDAZpKtfLZsFVVRng@mail.gmail.com>
 <bb7a9f8f-0422-45e5-b4fc-f5757add92b4@app.fastmail.com> <CAMW7n8BnzL7d0bd_Y_jGOmyWegKQpm-FzrVFRCcDe=bNFZpi+A@mail.gmail.com>
 <08c8ad0b-e8f4-46e3-99f0-b80748d40b89@app.fastmail.com> <07973EAE-2D83-47A8-8FA0-84286C77C02B@rwec.co.uk>
 <48d66433-3ae9-4895-8361-7c81a0a3670d@app.fastmail.com> <be7cb263-93a1-4bd8-9416-ae4d3e0bafe6@rwec.co.uk>
 <dbce8889-016a-4c59-864c-d8fdec895adc@app.fastmail.com> <CAM0Ccxh=bydoDEHBAV+Gb1_86HJjwhW06kzEsdRiMh93k1F7oA@mail.gmail.com>
 <8599eb8b-d4a3-4cb8-899a-25b134e0d64d@gmail.com> <D73BCCC4-3547-45B4-84AD-A5FD6569D43C@rwec.co.uk>
 <74c4c726-63aa-44e0-84c9-840e13a65a4f@gmail.com> <9b7ab30f-5ed6-400d-b941-1291e9185286@app.fastmail.com>
 <9a2e81e8-3534-455b-879a-5a45c85b3ba7@gmail.com> <CAMW7n8BRwZH64mULctRS4CxOL9TCo5GHvz-ORWHMZr926ZujYw@mail.gmail.com>
 <CAAwdEzALuRtkWyw1JgRVVmU9ew8uTiY6DSruR2CKiqNQ03QzOw@mail.gmail.com>
 <CAMW7n8A17ER8vUkNNrEsbkyGm2xY-ZAxkR1_ofWcHmgFbNrzqg@mail.gmail.com> <CAAwdEzBU2pttT5s8DFN1hfB-gS8-HKsAfDowuAj0BKaX007hDQ@mail.gmail.com>
In-Reply-To: <CAAwdEzBU2pttT5s8DFN1hfB-gS8-HKsAfDowuAj0BKaX007hDQ@mail.gmail.com>
Date: Sun, 9 Mar 2025 11:30:10 +0200
Message-ID: <CAMW7n8AAkkK12096h5hf6PsBB121RcfFx=Gd7n7nU-4yymhQdw@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP True Async RFC
To: =?UTF-8?Q?Alexandru_P=C4=83tr=C4=83nescu?= <drealecs@gmail.com>
Cc: Daniil Gentili <daniil.gentili@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000022b9b4062fe5810b"
From: edmond.ht@gmail.com (Edmond Dantes)

--00000000000022b9b4062fe5810b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

>
> Have a different method `Fiber::suspendToScheduler(Resume $resume)` that
would return the control to the Scheduler.
>

That's exactly how it works. The RFC includes the method Async\wait()
(Fiber::await() is nice), which hands control over to the Scheduler.
At the PHP core level, there is an equivalent method used by all blocking
functions. In other words, Fiber::suspend is not needed; instead, the
Scheduler API is used.

The only question is backward compatibility. If, for example, it is agreed
that the necessary changes will be made in Revolt when this feature is
released and we do not support the old behavior, then there is no problem.

>
>  Maybe that is what we need: to be able to return control both to the
parent fiber for custom logic that might be needed, and to the Scheduler so
that the language would be concurrent.
>

100% yes.

>
>  As for userland event loops, like Revolt, I am not so sure they fit with
the new language level async model.
>

Revolt can be adapted to this RFC by modifying the Driver module. I
actually reviewed its code again today to assess the complexity of this
change. It looks like it shouldn=E2=80=99t be difficult at all.

The only problem arises with the code that has already been written and is
publicly available. I know that the AMPHP stack is in use, so we need a
*flow* that ensures a smooth transition.

As I understand it, you believe that it=E2=80=99s better to introduce more =
radical
changes and not be afraid of breaking old code. In that case, there are no
questions at all.

>

--00000000000022b9b4062fe5810b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">&gt;<br>&gt; Have a different method `Fib=
er::suspendToScheduler(Resume $resume)` that would return the control to th=
e Scheduler.=C2=A0</div><div dir=3D"ltr">&gt;<br><p>That&#39;s exactly how =
it works. The RFC includes the method <code>Async\wait() (Fiber::await() is=
 nice)</code>, which hands control over to the Scheduler.<br>
At the PHP core level, there is an equivalent method used by all blocking f=
unctions. In other words, <code>Fiber::suspend</code> is not needed; instea=
d, the Scheduler API is used.</p>
<p>The only question is backward compatibility. If, for example, it is agre=
ed that the necessary changes will be made in Revolt when this feature is r=
eleased and we do not support the old behavior, then there is no problem.</=
p><p>&gt;<br>&gt;=C2=A0

Maybe that is what we need: to be able to return control both to the parent=
 fiber for custom logic that might be needed, and to the Scheduler so that =
the language would be concurrent.<br>&gt;</p><p>100% yes.</p><p>&gt;<br>&gt=
;=C2=A0

As for userland event loops, like Revolt, I am not so sure they fit with th=
e new language level async model.<br>&gt;</p><p>Revolt can be adapted to th=
is RFC by modifying the <code>Driver</code> module. I actually reviewed its=
 code again today to assess the complexity of this change. It looks like it=
 shouldn=E2=80=99t be difficult at all.</p><p>
</p><p>The only problem arises with the code that has already been written =
and is publicly available. I know that the AMPHP stack is in use, so we nee=
d a <strong>flow</strong> that ensures a smooth transition.</p><p>As I unde=
rstand it, you believe that it=E2=80=99s better to introduce more radical c=
hanges and not be afraid of breaking old code. In that case, there are no q=
uestions at all.</p></div><div class=3D"gmail_quote gmail_quote_container">=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto"><div cl=
ass=3D"gmail_quote" dir=3D"auto"><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex"><div dir=3D"ltr"><div><p></p></div></div>
</blockquote></div></div>
</blockquote></div></div>

--00000000000022b9b4062fe5810b--