GetWithExpirationUpdate - atomic implementation #125
Closed
Conversation
This file contains 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
…-new-map-design GetWithExpirationUpdate method and items are converted to pointers
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR is fixed version of #96. Main changes are:
cache.itemsare converted frommap[string]Itemtomap[string]*Item. I needed to do it because, inGetWithExpirationUpdate, it is the only way to modify theExpirationfield of anItem. The other way around (re-setting the item) needs a write lock, therefore blocks all reads/writes toitems. Not convenient for 'cache-get's.Itemhas its ownRWLock. This way, we don't need a write lock inGetWithExpirationUpdate.