socket.io-redis-adapter
socket.io-redis-adapter copied to clipboard
Adapter to enable broadcasting of events to multiple separate socket.io server nodes.
sorry this is just a question io.sockets.sockets is the list of all sockets is this adapter update this list ? (" Note: no data is stored in Redis itself ")
i am using pm2 cluster mode for my node app and when i try to fetch socket via ``` // return all Socket instances in the "room1" room of the...
The `@socket.io/redis-emitter` library had a recent major update that brought a new major version of the underlying `notepack.io` library to fix an issue handling `BigInt`, and so has the patch...
When using the sharded adapter with `subscriptionMode: "dynamic"`, messages sent to the socket's private room via `socket.emit()` get lost without any warning or error. It happens because [in this check](https://github.com/socketio/socket.io-redis-adapter/blob/ef5f0da0b4928fd422afc985aec0e233d34400c0/lib/sharded-adapter.ts#L127-L131),...
As an alternative solution for #524, this: - adds a new option `dynamicPrivateChannels`, which allows creating separate channels even for private rooms; defaults to `false` so there's no change in...
Fixes #524 by adding a check for `expectSingleResponse` flag, which is added for `RemoteSocket` instances [here](https://github.com/socketio/socket.io/blob/54dabe5bffeb705fd006729725dd2fa194f70ecf/lib/broadcast-operator.ts#L491). I couldn't find any documentation about that flag, but it seems to be the...
We are using two version of socket io. For v2.5.0 => "socket.io-redis": "^5.4.0" v4.7.1 => @socket.io/redis-adapter": "^8.0.1" transport is working fine when we are pushing the messages but whenever we...
"socket.io": "^4.5.4" "@socket.io/redis-adapter": "^8.0.0", AWS elastic cache - redis engine version - 6.2.6 Above are the version in my application running on mutliple container and i'm getting this error when...
Hi, We are using socket.io-redis-adapter to link sockets shared between several servers. At some point after the servers restart, the pubClient in the redis adapter becomes unready, and completely blocks...
In the redis sharded adapter, you should be able to optionally specify a channel name to emit "serverSideEmit" or "fetchSockets" to limit network activity in some cases where you know...