@tdykstra A few problems here:

We also have the <distributed-cache> TH. Given that we probably need to get into the cache repository options there, it will probably double the content that we need to provide.
As it stands, the explanation of response caching in the Response Caching doc is tightly linked to headers that influence caching and the caching of entire responses. It's possible that the TH caching should be in its own doc. Note that ...
- The Tag Helpers can vary-by-header, but the system isn't so tightly bound to headers. For example, caching can be set to absolute or sliding expiration, which is effective regardless of request headers.
- The Tag Helpers can cache parts of responses (i.e., the content bound by the tag), and the content can be Razor content. They don't really do "response caching." It's more like "content caching" or something.
These two Tag Helpers could also either have their own sample (if they're described in their own doc) or get rolled into the existing sample if the Response Caching doc is rewritten.
Finally, there's the high level issue of what to do about all of the Tag Helpers and their docs. Does each of the ~17 MVC Tag Helpers deserve its own doc? If things went that way, then the Response Caching doc really would just link to it in its Resource section or with just a couple of lines in a section at the bottom of the doc.

Another alternative here is to punt 🏈 : Mention that these Tag Helpers exist in a section at the end of the doc and then link to the .NET Monsters video on the subject on Channel 9: https://channel9.msdn.com/Series/aspnetmonsters/Episode-35-Distributed-Cache-Tag-Helper

How do you want to proceed?

Document cache tag helper in response caching doc #1948

Description