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
{{ message }}
This repository has been archived by the owner on Oct 15, 2021. It is now read-only.
Currently, all events broadcasted from the server are sent over the wire to all clients. While this is expected behaviour, it is sometimes undesirable.
I propose using the pub/sub pattern where clients can subscribe to specific RPC methods and only receive messages for those methods that the client subscribed to.
By default, the server, would send messages for a specific method only to the clients that subscribed to that method.
E.g. of subscribe RPC:
{"jsonrpc": "2.0","method": "subscribe",// "unsubscribe" when user don't want messages for the method anymore"params": {"method": "SOME_METHOD"}}
The text was updated successfully, but these errors were encountered:
Currently, all events broadcasted from the server are sent over the wire to all clients. While this is expected behaviour, it is sometimes undesirable.
I propose using the pub/sub pattern where clients can subscribe to specific RPC methods and only receive messages for those methods that the client subscribed to.
By default, the server, would send messages for a specific method only to the clients that subscribed to that method.
E.g. of subscribe RPC:
The text was updated successfully, but these errors were encountered: