Add concept of connectors to cacheables#9
Open
bwees wants to merge 2 commits intogrischaerbe:masterfrom
Open
Conversation
defaults to the original memory cache but the memory cache is broken into its own class
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 allows a custom cache connector to replace the in-memory cache. This PR retains the default behavior of the library (in-memory cache) but allows you to specify a connector that implements
CacheConnector. This will allow users to implement databases such as Redis or other KV stores as cache storage.The in-memory cache has been broken into its own class that implements
CacheConnectorto simplify the code. This class is used by default if a connector is not specified.