Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126538
Feedback-ID: ifab94697:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Sat, 01 Mar 2025 10:22:49 +0100
To: internals@lists.php.net
Message-ID: <25697b0c-a63e-4b47-86d6-844747b88d22@app.fastmail.com>
In-Reply-To: 
 <CAMW7n8AJckEDzhGv9BdjNhq8zAdCqb4HsVr56vGi+izw50X6Dg@mail.gmail.com>
References: 
 <CAMW7n8AJckEDzhGv9BdjNhq8zAdCqb4HsVr56vGi+izw50X6Dg@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP True Async RFC
Content-Type: multipart/alternative;
 boundary=920589e59b9a40ddac3fd1ec669e6d78
From: rob@bottled.codes ("Rob Landers")

--920589e59b9a40ddac3fd1ec669e6d78
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Sat, Mar 1, 2025, at 10:11, Edmond Dantes wrote:
> Good day, everyone. I hope you're doing well.
>=20
> I=E2=80=99d like to introduce a draft version of the RFC for the True =
Async component.
>=20
> https://wiki.php.net/rfc/true_async
>=20
> I believe this version is not perfect and requires analysis. And I str=
ongly believe that things like this shouldn't be developed in isolation.=
 So, if you think any important (or even minor) aspects have been overlo=
oked, please bring them to attention.
>=20
> The draft status also highlights the fact that it includes doubts abou=
t the implementation and criticism. The main global issue I see is the l=
ack of "future experience" regarding how this API will be used=E2=80=94a=
nother reason to bring it up for public discussion.
>=20
> Wishing you all a great day, and thank you for your feedback!
>=20

FYI: once you introduce a draft RFC for discussion, the RFC should chang=
e status to "under discussion" per (4): https://wiki.php.net/rfc/howto

=E2=80=94 Rob
--920589e59b9a40ddac3fd1ec669e6d78
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Sat, Mar 1, =
2025, at 10:11, Edmond Dantes wrote:<br></div><blockquote type=3D"cite" =
id=3D"qt" style=3D""><div dir=3D"ltr"><div><p>Good day, everyone. I hope=
 you're doing well.<br></p><p>I=E2=80=99d like to introduce a draft vers=
ion of the RFC for the True Async component.<br></p><p><a href=3D"https:=
//wiki.php.net/rfc/true_async">https://wiki.php.net/rfc/true_async</a><b=
r></p><p>I believe this version is not perfect and requires analysis. An=
d I strongly believe that things like this shouldn't be developed in iso=
lation. So, if you think any important (or even minor) aspects have been=
 overlooked, please bring them to attention.<br></p><p>The draft status =
also highlights the fact that it includes doubts about the implementatio=
n and criticism. The main global issue I see is the lack of "future expe=
rience" regarding how this API will be used=E2=80=94another reason to br=
ing it up for public discussion.<br></p><p>Wishing you all a great day, =
and thank you for your feedback!<br></p></div></div></blockquote><div><b=
r></div><div>FYI: once you introduce a draft RFC for discussion, the RFC=
 should change status to "under discussion" per (4):&nbsp;<a href=3D"htt=
ps://wiki.php.net/rfc/howto">https://wiki.php.net/rfc/howto</a><br></div=
><div><br></div><div id=3D"sig121229152">=E2=80=94 Rob<br></div></body><=
/html>
--920589e59b9a40ddac3fd1ec669e6d78--