You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But, in the README.md file, you are suggesting prefix + '#' + namespace + '#' + room + '#' will be the way to distribute a message to a specific room.
I would also add what is the behavior when subscribing to a channel. For example, if room A is at server 1 and room B is at server 2, does sever1 will receive messages that are related to server2 (the load-balancer somehow magically did that each room belongs to 1 server, leave the optimization aside of that ;) )
It's implemented only in the sharded redis adapter? from the code it seems like, but not from the docs
Thanks! Please let me know if I can help somehow with the questions above :))
-m
The text was updated successfully, but these errors were encountered:
MatanYemini
changed the title
Unclear documentation around "channels"
Unclear documentation around "channels" + "local" emit
May 27, 2023
MatanYemini
changed the title
Unclear documentation around "channels" + "local" emit
Unclear documentation around "channels"
May 27, 2023
Hi!
1 question:
From what it seems that channels are according to "namespace" only, and not by roomId.
e.g:
this.channel = prefix + "#" + nsp.name + "#"; this.requestChannel = prefix + "-request#" + this.nsp.name + "#"; this.responseChannel = prefix + "-response#" + this.nsp.name + "#"; this.specificResponseChannel = this.responseChannel + this.uid + "#";
But, in the README.md file, you are suggesting
prefix + '#' + namespace + '#' + room + '#'
will be the way to distribute a message to a specific room.I would also add what is the behavior when subscribing to a channel. For example, if room A is at server 1 and room B is at server 2, does sever1 will receive messages that are related to server2 (the load-balancer somehow magically did that each room belongs to 1 server, leave the optimization aside of that ;) )
It's implemented only in the sharded redis adapter? from the code it seems like, but not from the docs
Thanks! Please let me know if I can help somehow with the questions above :))
-m
The text was updated successfully, but these errors were encountered: