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
Currently, if I want to use my own storage mechanism (that's not Redis) for OutputCaching, I have to create a "HybridOutputCacheStore", and an extension method "AddHybridOutputCache()" to register the service in my middleware since "AddOutputCache()" just adds the MemoryOutputCacheStore be default.
Are their any plans to "officially" support the practice of OutputCaching with HybridCache? Theoretically it would just require replacing the MemoryOutputCacheStore implementation with a HybridOutputCacheStore implementation that using HybridCache and IDistributeCache. Assuming the tagging issues are still being addressed and ultimately fixed, does this seems like the next logical step?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently, if I want to use my own storage mechanism (that's not Redis) for OutputCaching, I have to create a "HybridOutputCacheStore", and an extension method "AddHybridOutputCache()" to register the service in my middleware since "AddOutputCache()" just adds the MemoryOutputCacheStore be default.
Are their any plans to "officially" support the practice of OutputCaching with HybridCache? Theoretically it would just require replacing the
MemoryOutputCacheStore implementation with a HybridOutputCacheStore implementation that using HybridCache and IDistributeCache. Assuming the tagging issues are still being addressed and ultimately fixed, does this seems like the next logical step?
Source code: https://github.com/amiriltd/hybrid-output-cache
Beta Was this translation helpful? Give feedback.
All reactions