App specific listeners for swoole events

[Matthew Weier O'Phinney]

• I was not able to find an open or closed issue matching what I'm seeing.
• This is not a question. (Questions should be asked on chat (Signup here) or our forums.)

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

// This does not work as "SwooleServer::on()" supports only one listener
// and there is already a listener in SwooleRequestHandlerRunner
$masterServer = $container->get(SwooleHttpServer::class);
$masterServer->on('workerstart', function (SwooleHttpServer $workerServer) {
    $queue = \GuzzleHttp\Promise\queue();
    $workerServer->tick(100, function () use ($queue) {
        $queue->run();
    });
});

// I had to extend SwooleRequestHandlerRunner
// and copy-past SwooleRequestHandlerRunnerFactory
// to use an own event manager to add application specific listeners to these events
$em = $container->get(EventManagerInterface::class);
$em->attach(WorkerStartEvent::class, function (WorkerStartEvent $event) {
    $queue = \GuzzleHttp\Promise\queue();
    $workerServer = $event->getServer();
    $workerServer->tick(1000, function () use ($queue) {
        $queue->run();
    });
});

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-pasting SwooleRequestHandlerRunnerFactory.

---

Originally posted by @marc-mabe at zendframework/zend-expressive-swoole#69

[Matthew Weier O'Phinney]

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.

[Marc Bennewitz]

@weierophinney this would be an awesome solution.

[Mukhamad Ikhsan]

@weierophinney It's the code will be like that?