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
Client should have a way that allows users to force reconnection process.
This can be useful for refreshing auth or rebalancing clients.
When triggered, client will drop connection to the current server and perform standard reconnection process.
That means that all subscriptions and consumers should be resubscribed and their work resumed after successful reconnect where all reconnect options are respected.
For most clients, that means having a reconnect method on the Client/Connection handle.
You could make a custom AuthHandler that reacts the way you want and is aware of changes. This might even be a good addition to the project, would you be interested in trying to contribute?
Overview
Client should have a way that allows users to force reconnection process.
This can be useful for refreshing auth or rebalancing clients.
When triggered, client will drop connection to the current server and perform standard reconnection process.
That means that all subscriptions and consumers should be resubscribed and their work resumed after successful reconnect where all reconnect options are respected.
For most clients, that means having a
reconnect
method on the Client/Connection handle.Connection spec has been updated in #258
ADR Issue
nats-io/nats-architecture-and-design#259
The text was updated successfully, but these errors were encountered: