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
It could be more convenient to reconnect an existing instance based on some user side logic rather then create a new instance after disconnection of a current one. One option is to configure one of existing socket providers, another is to create a user own socket provider. However it may be simpler to catch the disconnected state situation and reconnect the client from an external code.
It may matter more for the cluster client that is bootstrapped from a one instance and uses cluster discovery to find others. If a need to reconnect occurs during a problem on the initial instance, reconnecting of an existing client will allow to bootstrap using instances from a last cluster discovery.
The text was updated successfully, but these errors were encountered:
It could be more convenient to reconnect an existing instance based on some user side logic rather then create a new instance after disconnection of a current one. One option is to configure one of existing socket providers, another is to create a user own socket provider. However it may be simpler to catch the disconnected state situation and reconnect the client from an external code.
It may matter more for the cluster client that is bootstrapped from a one instance and uses cluster discovery to find others. If a need to reconnect occurs during a problem on the initial instance, reconnecting of an existing client will allow to bootstrap using instances from a last cluster discovery.
The text was updated successfully, but these errors were encountered: