Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128912
Message-ID: <c6ae9798-40e9-4a14-8e4a-94244506cb94@alec.pl>
Date: Wed, 22 Oct 2025 21:19:24 +0200
Precedence: list
MIME-Version: 1.0
Subject: Re: [PHP-DEV] PHP True Async RFC Stage 4
To: internals@lists.php.net
References: <CAMW7n8DGbFnQzjt3s9CcOBwhp+MUOV+K3U=yY=ULOTdUXaOLHQ@mail.gmail.com>
 <25be6748-d8c3-4f1a-bf81-297cea72f8db@alec.pl>
 <CAMW7n8COoVPnzJx3u9mtBxHZn92xXYUija0T8GfP9d0rTgXw3g@mail.gmail.com>
Content-Language: en-US
Autocrypt: addr=alec@alec.pl; keydata=
 xsBNBEy9TtkBCAC4ef0IJaqTDQNQZ5CPrHvNs5kcACvtffwydrTcRJ28dHwjZD8daSxfVYEo
 acyARevTOvsp36Vgq8Yt7ATu6y7MPBaPj9Lq0kwX7HM8QDn8jTfufAgMjxcw5bD+JNR5+8G9
 hUF3F35gVuAd471hS+QB/Ug/PezcNx9H5yFUMuvrO3ybyIDhw5qJI2RoJMjMr5DPKUG7z810
 1e/NW7y9FfHq+Ony7A70w+vcfv1L+LLX5gfrpKI3m0zKm7cj1vyxZfC9RijIzWZN3GgExexI
 KJdbkcg9F/zigKo72TJhgvjy6YZP03HmWZVcpsd3aIT3Tweg0cCivaKVBNcFR1oda6XvABEB
 AAHNFkEuTC5FLkMgPGFsZWNAYWxlYy5wbD7CwHsEEwECACUCGyMGCwkIBwMCBhUIAgkKCwQW
 AgMBAh4BAheABQJMvVAwAhkBAAoJEL7mdKAZNZ3BEhkH/1eAuCOSXsWg8YwZzmABoKKZfNpJ
 Z3QTwAMxXyCPjJMwLMLHsrVO+VbGupFcIW/q/3bvt1r8LwPB73rg0TFiHoYzeQzdnOVYFW7w
 OYz9BDVjLE4goDk6xN5Nj1CpBMXzQFdr3HVKyuRK1CLd9p13CofiBlLsQ4JqtosnlvSCEjTL
 yIajACU3kY2je1e58N5VHzZ+VMeg2xbuQJ3q1iTkYggZ+xRC1muw4Xgt2vxgfWjn7u3dmjYM
 T3H2WFprLZwliejHgzhWdYABdyCU5VuGCLOV+xk2UCADya0hvVVIezA/4YG3w01yjsljRrKy
 HFJUqw+MqagA6dsfflZSvmROKMbOwE0ETL1O2QEIANHbid+rMQ/IX0/UyVtnLWunDEg6Yl2B
 twHTecZ4Ym3tBxc1sbPDoYpY0DZ86gYi9DCbolrdjnrRK9ldYItVJ8rJUkEIDz/2yhjcr3s3
 p2SyI94bocoG0WW+VRlssJMxTB2ihblihkY5HqT+9PgOFxnpSqz1ksTaI3JOVcokidhoB7MJ
 muyb28rNtZCJP7upRUwBSoZfHiL83w3Ad1Fn49QVO7kshH11lNyJ9jB17BTl1I0sj7RPqAor
 JcMxsSOJXW71ZcipXWym+GacY/qziQw7bT9CQYSmr4SiRV7GahD91enDkdv+pUAnb8NEifQ1
 LT26XcL6Ng9EbG5AT4qI46kAEQEAAcLAXwQYAQIACQUCTL1O2QIbDAAKCRC+5nSgGTWdwe2T
 CACaux3lHitD8IIO5fy6RxPqym6vMlKiN0IyilahtJ0A2htNqwbFb6TukpzKw04DGSPEOGPa
 o4hdsLtQtqAPwqrR+FGJDc6V/jD0rPjThC3NcvkJuoi622ZLCsi8TAL5kBmF2NYd7ejszB31
 5EzvpXSeES8+9pv6yshzUborEg9QKhPxW0yvrdj2OwFUlRr6/jLpKmMLzSx5F0yEg10urvfe
 9Sttk5TVzHycOa1nKSzj79F1jXTl/mji/i082s1nlwb8d6LNVrm0e1tGMxSk/WpghFVVSm4O
 MvUvMkEEDkwGsm+mPcmX4UPcvq/wU3hGhDeVlpkfVTJQGvDbEUzTXbz6
In-Reply-To: <CAMW7n8COoVPnzJx3u9mtBxHZn92xXYUija0T8GfP9d0rTgXw3g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
From: alec@alec.pl (Aleksander Machniak)

On 22.10.2025 19:01, Edmond Dantes wrote:
>> - The glossary in "Overview" is good, but probably incomplete. The
>> examples there, with no description, do not help much and could be
>> removed, imo.
> 
> Do I understand correctly that I should remove the examples without
> descriptions?

Examples in the Overview section aren't very helpful. I would remove 
them from there, but maybe some of them need to appear later. I didn't 
read it that carefully to suggest precise changes.

> Or would it be better to add descriptions to them?
> Although the last examples might not be very illustrative or easy to grasp.
> 
>> the "Scheduler and Reactor" section does not explain much over what's in the glossary.
> 
> What else do you think could be added?
> The internal implementation doesn’t belong in the scope of the RFC, it
> can change.
> They don’t have any special API in the PHP userland.
> The reactor can only be used directly at the C/C++ level, meaning
> within a PHP extension.
> It’s also intentionally impossible to directly affect the Scheduler’s behavior.

I think that it might be better to not mention them at all in the RFC. 
Or better separate parts that describe userland and engine. The 
structure of the Proposal is a bit chaotic.

-- 
Aleksander Machniak
Kolab Groupware Developer        [https://kolab.org]
Roundcube Webmail Developer  [https://roundcube.net]
----------------------------------------------------
PGP: 19359DC1 # Blog: https://kolabian.wordpress.com