-
Notifications
You must be signed in to change notification settings - Fork 224
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
Is this client considred thread-safe ? #46
Comments
The
However, being The More importantly, So.... IF you are not mutating your If there's demand for making |
@steve-perkins thanks for responding. The above usage pattern sound reasonable, As for the |
Sure! If you have any design proposals or want to try putting together a PR, I'd love to go over it. It may be a week or before I could get to it personally. The solution may be as simple as adding It just worries me that these |
@steve-perkins Has your answer on this changed since you made it? Are there any other potential edge-conditions in using this between threads? Depending on your answer, I could potentially open a PR to make it fully thread safe, or open a PR to document any concurrency considerations. Thanks in advance! This looks like a great client. |
Thanks, @NathanC. I'm certainly OPEN to the idea of making it possible and safe to swap out a Either way, I would be extremely appreciative of any investigation or documentation around other concurrency considerations in general. I personally just don't share |
Deprecates the App ID backend. Adds a new version of the Userpass backend.
Can I share a single Vault instance between multiple threads ?
The text was updated successfully, but these errors were encountered: