This repository was archived by the owner on Dec 5, 2024. It is now read-only.
Calling CacheHasBeenInvalidated instead of RefreshCache #689
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
At this point we know these values have already been marked as invalid. There is no reason to call RefreshCache on them and go through that pipeline again. Furthermore that pipeline is currently waiting for valid data, so it will not fire off the invalidation events a second time.
shana
approved these changes
Apr 12, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes #679
At the point that cacheInvalidationRequests are being handled, we already know the data is invalid.
There is no reason to call RefreshCache on them and go through that pipeline again.
Furthermore that pipeline is currently waiting for valid data, so it will not fire off the invalidation events a second time.