We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there a reason why the config is a global variable?
This scheme makes it difficult to create different connections, as the config is centralized and there is no way to override it.
It is relatively insecure or at least not ideal to be replacing the config to be able to keep different connections.
I would like to recommend having an approach where you can create a client instance with a configuration and set of parameters.
This will allow the user to create diverse connections on the same node instance if required.
The text was updated successfully, but these errors were encountered:
Upvoted! I have the same request. My app makes multiple connections and replacing the config feels unsafe
Sorry, something went wrong.
ISAAC-XXYYZZ
No branches or pull requests
Is there a reason why the config is a global variable?
This scheme makes it difficult to create different connections, as the config is centralized and there is no way to override it.
It is relatively insecure or at least not ideal to be replacing the config to be able to keep different connections.
I would like to recommend having an approach where you can create a client instance with a configuration and set of parameters.
This will allow the user to create diverse connections on the same node instance if required.
The text was updated successfully, but these errors were encountered: