CacheManager v0.9.3 Release Notes
Release Date: 2017-02-03 // about 7 years ago-
🚀 This release has some new features and fixes.
🆕 New Features
- 👍 Exists method to check if the key exists without actually retrieving it (if supported by the cache vendor) #46
- ➕ Added more "knownTypes" to Microsoft.Extensions.Configuration based CacheManager configuration's json schema #125 #123
- for the Microsoft.Extensions.Caching.MemoryCache based cache handle
- Protobuf serializer
- GzJson serializer
- 👍 Allow Memcached and Redis cache handles to use pre existing cache clients. The clients can now be passed into the configuration methods
WithRedisConfiguration,WithMemcachedHandle. #118
Other Changes
- Instead of CacheManagerConfiguration now ICacheManagerConfiguration will be used everywhere (more injection friendly)
- 👌 Improved validation at configuration time in case a cache handle requires a serializer, but none is defined (only net core target as full framework falls back to binary).
- 🏗 custom serialization logic for memcached to use our cache serializers instead of the build in binary.
- ➕ Added overload to configure binary serializer settings during configuration.
🐛 Bug fixes
- ⏱ Validate expiration timeout not being in the past #74
- ⚡️ Changed update mechanism in the redis implementation to use a version field #109
- 🛠 Fixed a bug where the mechanic in CacheManager which adds a key/value to other cache handles does not correctly apply expiration settings based on the cache handle configuration when it comes from Redis.
- other minor things
Please report any bugs or issues you find on github