Is there any intention to create a PHP RFC for a Fiber scheduler?

[EdmondDantes]

Good day,

I would like to once again express my gratitude to all the developers of this project. Thanks to your code, I have learned a lot about implementing asynchronous programming. I really appreciate the efficient approach to creating fibers. It's awesome!

However, I am unpleasantly surprised by what is happening at the PHP language level.

PHP has fibers, and that was a significant change, but not sufficient.

For the language to fully support asynchronous programming, an API is needed.

An API is needed that would allow transferring control from the fiber context to the scheduler.

For example, let's assume the code uses a PHP function like socket read/write. At the moment of invocation, this function could determine whether it is being executed inside a fiber. If so, it immediately passes its I/O descriptor, additional options, and invokes the scheduler.

The Scheduler API then transfers control to code that decides how to proceed with context switching, which objects to wait for, and so on.

PHP already has a similar implementation at the Zend level—Swoole—which uses hooks to override the behavior of standard functions.

But why hasn’t this been standardized yet? Such an API would save time when creating libraries, avoiding the need to clone PDO and similar tools.

Thank you once again for your contribution.

[Bilge]

Yes.

[EdmondDantes]

Yes.

So, this RFC exists, but it’s not publicly available yet?

[Bilge]

You asked if there are plans. There are plans. Don't let that stop you if you want to propose one, though.

…

On Sun, 24 Nov 2024, 16:13 Edmond, ***@***.***> wrote: Yes. So, this RFC exists, but it’s not publicly available yet? — Reply to this email directly, view it on GitHub <#447 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADS4YWA2UDPTPJREG74VH32CH3J7AVCNFSM6AAAAABSLZQN2SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJWGA4TAMRYHE> . You are receiving this because you commented.Message ID: ***@***.***>