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 }}
Repository navigation
Proposal : Rename to ASPNetCoreMVC.OutputCaching #2
Hi, I came across this intrigued due to the name but then looked at the source and README and realised it relies on things in MVC to cache the responses as well as a dependency on MVC itself.
How would you feel about renaming it to be more explicit?
There are frameworks/libraries that run on top of asp.net core that dont use MVC so having middleware to do caching would be great but they won't want/need the MVC dependency. We have to be careful with the naming, that's all I'm highlighting.
Activity
JuergenGutsch commentedon Oct 20, 2017
I'd like to have the name Microsoft.AspNetCore.OutputCaching and moved then to the ASP.NET Core Caching repo: https://github.com/aspnet/Caching/ ;-)
jchannon commentedon Oct 20, 2017
There are frameworks/libraries that run on top of asp.net core that dont use MVC so having middleware to do caching would be great but they won't want/need the MVC dependency. We have to be careful with the naming, that's all I'm highlighting.
Julien-Marpault commentedon Dec 22, 2017
What is the benefit of this extension compaed to built-in .net core caching?