Memory leak prevention on using authentication tokens #98
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For each command is executed through SwiftClient a new listener is created in OpenStack.CLIENT.listeners . In order to avoid filling the memory with the same listener again and again, I have created the endpoint just once for each SwiftClient instance.
The user token must be set per transaction, instead of creating a new listener in OpenStack.CLIENT every time the SwiftClient.execute method is called.
Collaborator
|
This looks good, @efoncubierta can you do a pull request against master? Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch fixes issue #97
I have included @rbramley changes as well.