Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129338
Precedence: list
MIME-Version: 1.0
References: <CAMW7n8D0QshP8VhGOUqVnC+Uwf88TC_yy_mQdeNZW_go5YLdcw@mail.gmail.com>
In-Reply-To: <CAMW7n8D0QshP8VhGOUqVnC+Uwf88TC_yy_mQdeNZW_go5YLdcw@mail.gmail.com>
Date: Thu, 20 Nov 2025 19:06:35 +0100
Message-ID: <CABdc3WpkB-Mm0qDe-ajWTr1Pq8Qb4dXQcoNwdzgR49m1OO44tQ@mail.gmail.com>
Subject: Re: [PHP-DEV] [VOTE] True Async RFC 1.6
To: Edmond Dantes <edmond.ht@gmail.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000689db306440a8ff7"
From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Marcin_Brzuchalski?=)

--000000000000689db306440a8ff7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=C5=9Br., 19 lis 2025 o 13:36 Edmond Dantes <edmond.ht@gmail.com> napisa=C5=
=82(a):

> Hello all
>
> According to all previous discussions, version 1.6 of this RFC has
> been prepared and is now being submitted for a vote:
>
> Voting Page: https://wiki.php.net/rfc/true_async/voting
> RFC https://wiki.php.net/rfc/true_async
>
> The vote officially starts tomorrow, as previously announced.
>
> For version 1.6 the following important change was made:
> All input/output functions are now bound by the shared requirement of
> being non-blocking with respect to the process. However, the specific
> behavior of each function may (optionally) be defined in separate
> RFCs.
>
> Thus, I/O functions themselves are not part of this RFC, but the main
> RFC defines the general way in which they must operate. Thus (as I see
> it), the RFC achieves a balance between cohesion and separation of
> concerns.
>
> Since the discussion period has ended, I will not be engaging in
> further debate (except regarding the voting process itself). If you
> have any questions for me of any kind, you may ask them either in a
> separate thread or privately. (This also means that I will not be
> answering RFC-related questions in this thread). I will be glad to
> hear your opinions and feedback. I wish all participants the best of
> luck.
>
> ---
> Best Regards, Ed
>

Just a quick clarification regarding my vote.

I cast a =E2=80=9Cyes=E2=80=9D because I wanted to express general support =
for the idea of
native async in PHP, not because I believed the RFC in its current form was
ready to pass. The ongoing discussion clearly shows there are still open
questions to resolve, and I fully respect that.

My intention was simply to show encouragement for the direction and
acknowledge the work that went into this effort, even if this particular
iteration is unlikely to succeed. I=E2=80=99m absolutely fine with the vote
continuing or being paused if needed =E2=80=94 whatever best serves the pro=
cess.

Regardless of the outcome, I hope the exploration of async in PHP
continues. It=E2=80=99s an important topic, and I appreciate the dedication=
 behind
the proposal.

Cheers,
--
Micha=C5=82 Marcin Brzuchalski

--000000000000689db306440a8ff7
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">=C5=9Br., 19 li=
s 2025 o 13:36=C2=A0Edmond Dantes &lt;<a href=3D"mailto:edmond.ht@gmail.com=
">edmond.ht@gmail.com</a>&gt; napisa=C5=82(a):<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">Hello all<br>
<br>
According to all previous discussions, version 1.6 of this RFC has<br>
been prepared and is now being submitted for a vote:<br>
<br>
Voting Page: <a href=3D"https://wiki.php.net/rfc/true_async/voting" rel=3D"=
noreferrer" target=3D"_blank">https://wiki.php.net/rfc/true_async/voting</a=
><br>
RFC <a href=3D"https://wiki.php.net/rfc/true_async" rel=3D"noreferrer" targ=
et=3D"_blank">https://wiki.php.net/rfc/true_async</a><br>
<br>
The vote officially starts tomorrow, as previously announced.<br>
<br>
For version 1.6 the following important change was made:<br>
All input/output functions are now bound by the shared requirement of<br>
being non-blocking with respect to the process. However, the specific<br>
behavior of each function may (optionally) be defined in separate<br>
RFCs.<br>
<br>
Thus, I/O functions themselves are not part of this RFC, but the main<br>
RFC defines the general way in which they must operate. Thus (as I see<br>
it), the RFC achieves a balance between cohesion and separation of<br>
concerns.<br>
<br>
Since the discussion period has ended, I will not be engaging in<br>
further debate (except regarding the voting process itself). If you<br>
have any questions for me of any kind, you may ask them either in a<br>
separate thread or privately. (This also means that I will not be<br>
answering RFC-related questions in this thread). I will be glad to<br>
hear your opinions and feedback. I wish all participants the best of<br>
luck.<br>
<br>
---<br>
Best Regards, Ed<br></blockquote><div><br></div>Just a quick clarification =
regarding my vote.<br><br>I cast a =E2=80=9Cyes=E2=80=9D because I wanted t=
o express general support for the idea of native async in PHP, not because =
I believed the RFC in its current form was ready to pass. The ongoing discu=
ssion clearly shows there are still open questions to resolve, and I fully =
respect that.<br><br>My intention was simply to show encouragement for the =
direction and acknowledge the work that went into this effort, even if this=
 particular iteration is unlikely to succeed. I=E2=80=99m absolutely fine w=
ith the vote continuing or being paused if needed =E2=80=94 whatever best s=
erves the process.<br><br>Regardless of the outcome, I hope the exploration=
 of async in PHP continues. It=E2=80=99s an important topic, and I apprecia=
te the dedication behind the proposal.<br><div>=C2=A0</div><div>Cheers,</di=
v><div>--</div><div>Micha=C5=82 Marcin Brzuchalski</div></div></div>

--000000000000689db306440a8ff7--