Hi
Am 2026-07-02 16:53, schrieb Eric Norris:
(Tim, I've not added you as an author since I wasn't sure you'd be
cool with that, but if you'd like I would be more than happy to.)
I'm okay with that.
------
And with regard to the RFC itself: Leaving the “Open Issues” and “Future
Scope” sections empty looks weird. I suggest to either remove them
completely or insert an explicit “None” or so. The same is true for the
SAPI impact. The changelog could just be an "- 2026-07-02: Initial
version" and then "- 2026-07-02: Clarify impact" (see below).
The “References” section should ideally include links to the Pre-RFC
discussion thread and must include a link to this discussion. For your
convenience: https://news-web.php.net/php.internals/131707 +
https://news-web.php.net/php.internals/130704).
An “ecosystem impact” of “None” is also almost always wrong. I would
mention the following (perhaps with a little nicer phrasing).
- For COM_RESET_CONNECTION: The proper reset on persistent connections
has the (positive) impact that the behavior of persistent connections
will be more predictable. Of course if folks rely on some connection
state carrying over across requests, they might see a breaking change.
- Users that want to use the newest PHP version will be required to also
run newer versions (released in the last 5 years) of other software.
Best regards
Tim Düsterhus
