Rewrote CachingConnector as decorator #44
Closed
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 key change brings the following improvements to
CachingConnector.Connectorimplementations no longer have to extendCachingConnectorto provide caching facilities: all connectors can be decorated withCachingConnectorwith no prior knowledge of the existence of such facility. This completely removes the burden on implementations to be aware of caching concerns.Connectorimplementations to use however else they see fit.Technical changes
CachingConnectorfrom abstract class to concrete decorator.CachedAdvicewith simple boolean (cache or cache not; there is no try).Cacheinterface.SuperConnector->ImportConnector.