Closed weierophinney closed 3 years ago
I think the way to make this work is to have the various Swoole event listeners we register trigger their own events via a PSR-14 event dispatcher. This way, we can allow for scenarios like this.
Essentially, in SwooleRequestHandlerRunner
, for listeners such as public function onWorkerStart()
, they would read:
public function onWorkerStart(SwooleHttpServer $server, int $workerId): void
{
$this->dispatcher->dispatch(new OnWorkerStartEvent($server, $workerId));
}
We would then have a mechanism for adding listeners, and move the logic we currently have into those listeners.
@weierophinney this would be an awesome solution.
@weierophinney It's the code will be like that?
Use swoole tick timer on the worker process to be able to use it as the event loop for guzzle.
PS: By default guzzle uses PHP shutdown handler but this does not work in a swoole environment. To be able to use async Guzzle callbacks within an swoole worker you have to run the task queue of Guzzle manually. This can simply be done using the
SwooleServer::tick
function of the worker process.Code to reproduce the issue
Expected results
There should already be a way in zend-expressive-swoole to add application specific listeners to such events
Actual results
It's not possible without extending
SwooleRequestHandlerRunner
and copy-pastingSwooleRequestHandlerRunnerFactory
.Originally posted by @marc-mabe at https://github.com/zendframework/zend-expressive-swoole/issues/69