You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 14, 2018. It is now read-only.
Currently both interfaces has different methods and extensions, which is making switching between them quite hard. Also memory cache has more methods that simplifying usage of caching.
The text was updated successfully, but these errors were encountered:
msmolka
changed the title
Consider unirication between IMemoryCache and IDistributedCache.
Consider unification between IMemoryCache and IDistributedCache.
Aug 20, 2016
They can't be unified, that would be a breaking change. They shouldn't be unified, they have fundamentally different semantics. MemoryCache can store live objects, the distributed cache can't, objects have to be serialized. The distributed cache can be off box and calls to it may fail or take a long time so getting and setting should be async, the MemoryCache is always in memory and fast. The distributed cache can be disconnected from the store so the interface should account for that.
It's like trying to unify IDictionary<object, object> with a redis client interface. It's apples and oranges.
Currently both interfaces has different methods and extensions, which is making switching between them quite hard. Also memory cache has more methods that simplifying usage of caching.
The text was updated successfully, but these errors were encountered: