2 ms·
> Normally, non-cacheable page fragments would make every page uncacheable. AFAICT, ASP.NET supported partial output caching since 2003. And, it can store mult
by MichaelGG 12y ago
> Normally, non-cacheable page fragments would make every page uncacheable.
AFAICT, ASP.NET supported partial output caching since 2003. And, it can store multiple versions of a cached item via a user-defined parameter (a property on the cached control class). It seems it might be possible to simply create a property that returns the user ID and let the cache vary on that.
Of course, this uses the Web Forms controls-based system, which isn't very popular. But calling this type of caching new seems a bit of a stretch.
http://msdn.microsoft.com/en-us/library/k4he1ds5%28v=vs.71%29.aspx http://msdn.microsoft.com/en-us/library/k4he1ds5%28v=vs.71%2...
Edit: And here's a link talking about VaryByCustom, complete with example code that uses the version of the browser to generate unique per-browser-version caches.
http://msdn.microsoft.com/en-us/library/5ecf4420%28v=vs.71%29.aspx http://msdn.microsoft.com/en-us/library/5ecf4420%28v=vs.71%2...