In order to use node cluster with socket.io, multiple requests from the same client need to be routed to the same worker.
https://github.com/indutny/sticky-session does this, but integrating this with service-runner's master and worker code isn't straightforward (at least to me).
The setup for sticky session is different than plain ol' node cluster use. For sticky sessions, the master process needs to explicitly call server.listen, and then incoming connection handles can be sent to worker processes. This is how sticky-session works.
Since service-runner supports running multiple services via different service modules, integrating sticky support seems hard. service-runner expects each worker to call server.listen, which won't work for sticky-session.
Is this worth doing? I'd really like to use Kasocki in service-runner, but I'm not sure if fits the service-runner model. If not, I could just bring in a lot of the service-runner ideas and code into a fork or new repo and make it work with sticky-session.