Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129300
Precedence: list
MIME-Version: 1.0
Date: Wed, 19 Nov 2025 14:35:13 +0200
Message-ID: <CAMW7n8D0QshP8VhGOUqVnC+Uwf88TC_yy_mQdeNZW_go5YLdcw@mail.gmail.com>
Subject: [PHP-DEV] [VOTE] True Async RFC 1.6
To: php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
From: edmond.ht@gmail.com (Edmond Dantes)

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