Support output caching

[yishaigalatzer]

We need to design and support output caching for MVC actions. Along with integration to popular caching mechanisms

[tugberkugurlu]

@yishaigalatzer what are the current thoughts on HTTP caching? As MVC is now a unified framework which will also harbor the Web API, that would be something needed there.

[yishaigalatzer]

This is currently a need design item. More for tracking a replacement for the old https://aspnetwebstack.codeplex.com/workitem/608 and combine it with the MVC behavior.

That really means we haven't spent much time thinking about it yet. So if you have specific ideas for HTTP caching, it's a good place to add them. We are probably going to break this item down to more fine grained items.

[aliostad]

As you might know, I have implemented HTTP Caching in CacheCow library. I am happy to contribute towards building the feature.

[Eilon]

We're thinking of doing something at the middleware layer so that output caching is available to all other middleware components. Then frameworks such as MVC would merely be consumers of the output caching middleware and not implement any such caching on their own.

[aliostad]

Well Output Caching is better than nothing but there is more (way more) to HTTP caching than Output Caching.

Output Caching in ASP.NET MVC/Web API is user-mode and not Kernel mode and its rules are usually system-wide (2 requests within 2 minutes or something) and changing them requires registry change. Its capacity bound by the memory available on the server and once threshold reached, it suddenly chucks out half of its content.

I would like to see HTTP caching supported as a first class citizen.

[davidfowl]

@aliostad whatever we do will likely live in middleware or as part of the HttpAbstractions repository. Mvc will expose those primitives using things like filters.

[aliostad]

@davidfowl sure. So is there another thread somewhere else that we can carry on discussion?