Re: PHP True Async RFC Stage 4

From: Date: Mon, 06 Oct 2025 05:34:43 +0000
Subject: Re: PHP True Async RFC Stage 4
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-128785@lists.php.net to get a copy of this message
Hello.

> Just a quick question - other methods that tried to provide async/parallel type functionality
> previously were only available via the CLI.

TrueAsync itself is integrated into PHP in such a way that it is
always active. The scenario you described is technically possible (Of
course, this can also be useful for sending telemetry in a way that
doesn’t interfere with request processing.), but it’s not particularly
relevant in the context of modern development.

Why?

Because client requests are usually processed sequentially, step by
step. Parallel tasks are rare. Therefore, from the server’s
perspective, the main benefit of concurrency is the ability to handle
multiple requests within a single process. The same thing that Swoole,
AMPHP, and other modern backend solutions do.

And this is one of the reasons why FPM is morally outdated and
therefore not used in stateful backends. That’s why you encounter CLI
so often.


Thread (104 messages)

« previous php.internals (#128785) next »