Question: remote socket + event emitter ?

[fxi]

Hello,

Would it be possible to have/recreate a full Socket from fetchSockets instead of the partial RemoteSocket ? Currently, if the socket is not local, it lacks some EventEmitter methods and it's is blocking for a specific case on a cluster.

Maybe I missed something :/

Thanks

[darrachequesne]

@fxi you mean, having the on() method and such? In that case, that's not currently possible.

What you can do is use the serverSideEmit() method: https://socket.io/docs/v4/server-instance/#serversideemit

[fxi]

Yep, thanks.

That's exactly that : I was trying to catch an event from a non-local socket. It was not clear for me that on/once were not available on remote socket: during testing, I was on a single node. On multiple nodes, local sockets are complete but remote sockets are partial.

I was mixing HTTP request to launch a process and websocket to feedback progress and listen for data from the browser in an optional async task.

I started converting everything using websocket/socket.io, including authentication. That's a consequent change, but it will simplify the whole thing.

I also got a sticky session issue in the first place: our proxy/load-balancer only allows cookie based stickiness, and it does not work when cookies are not allowed. ws connection were kept on the same server as the ws connection, but subsequent request were done on any node. It's basic, but after reading the doc, I was convinced that fetchSockets and redis-adapter were the solution.

Anyway, thanks again !