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
Can you add a publish-subscribe model like redis to ensure that you can communicate between different threads and different machines, the current way it seems that all access is built within one thread. If a client connected by the current thread wants to communicate with a client saved on another machine, it cannot use getClientById to find another client connected by a different thread
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Can you add a publish-subscribe model like redis to ensure that you can communicate between different threads and different machines, the current way it seems that all access is built within one thread. If a client connected by the current thread wants to communicate with a client saved on another machine, it cannot use getClientById to find another client connected by a different thread
Beta Was this translation helpful? Give feedback.
All reactions