Skip to content
New issue

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

Allow for client instances instead of using global variables #10

Open
kvindascr opened this issue May 6, 2021 · 1 comment
Open

Allow for client instances instead of using global variables #10

kvindascr opened this issue May 6, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@kvindascr
Copy link

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.

@kvindascr kvindascr changed the title Remove global variables Allow for client instances instead of using global variables May 6, 2021
@DavidKrpt
Copy link

Upvoted! I have the same request. My app makes multiple connections and replacing the config feels unsafe

@ISAAC-XXYYZZ ISAAC-XXYYZZ self-assigned this Aug 13, 2024
@ISAAC-XXYYZZ ISAAC-XXYYZZ added the enhancement New feature or request label Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants