Re: [VOTE] True Async RFC 1.6

From: Date: Wed, 19 Nov 2025 16:58:21 +0000
Subject: Re: [VOTE] True Async RFC 1.6
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-129312@lists.php.net to get a copy of this message
Am 19.11.2025, 13:35:13 schrieb Edmond Dantes <edmond.ht@gmail.com>: > 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 > voted No soley because of the API design problems that Tim mentioned and needs to be addressed before voting. Its not a vote on the merits of the RFC in general. > 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 >

« previous php.internals (#129312) next »