Comments on: Setting HTTP Cache info using ASP.NET http://www.kongsli.net/nblog/2009/04/03/setting-http-cache-info-using-aspnet/ Deep thoughts on shallow topics Thu, 19 Aug 2010 09:56:57 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: vidarkongsli http://www.kongsli.net/nblog/2009/04/03/setting-http-cache-info-using-aspnet/comment-page-1/#comment-3774 vidarkongsli Tue, 14 Apr 2009 06:37:59 +0000 http://www.kongsli.net/nblog/2009/04/03/setting-http-cache-info-using-aspnet/#comment-3774 Hi Mark. Nice NCache pitch. ;) Thanks for your comment, NCache looks like an interesting technology. However, in my opinion it is not quite on target with respect to what the original blog post is about, namely how to set HTTP headers to enable caching in front of the web application (in proxies, browsers, etc.). Hi Mark. Nice NCache pitch. ;)
Thanks for your comment, NCache looks like an interesting technology. However, in my opinion it is not quite on target with respect to what the original blog post is about, namely how to set HTTP headers to enable caching in front of the web application (in proxies, browsers, etc.).

]]> By: Mark Jonathen http://www.kongsli.net/nblog/2009/04/03/setting-http-cache-info-using-aspnet/comment-page-1/#comment-3753 Mark Jonathen Thu, 09 Apr 2009 11:02:02 +0000 http://www.kongsli.net/nblog/2009/04/03/setting-http-cache-info-using-aspnet/#comment-3753 ASP.NET Cache being stand-alone & InProc is a problem. Trying to "simulate" distribution through SqlCacheDependency is really a "hack" in my opinion. The right way to solve this scalability problem is through an in-memory distributed cache. And, Microsoft is finally realizing it as well. They're working on Velocity but that is still in its infancy and will take some time to stabalize and mature. I personally like NCache which is really impressive because of its rich set of caching topologies (Mirrored, Replicated, Partitioned, Partition-Replica, and Client Cache). The cool thing is that it also has NCache Express which is free for 2-server environments. ASP.NET Cache being stand-alone & InProc is a problem. Trying to “simulate” distribution through SqlCacheDependency is really a “hack” in my opinion. The right way to solve this scalability problem is through an in-memory distributed cache.
And, Microsoft is finally realizing it as well. They’re working on Velocity but that is still in its infancy and will take some time to stabalize and mature.

I personally like NCache which is really impressive because of its rich set of caching topologies (Mirrored, Replicated, Partitioned, Partition-Replica, and Client Cache). The cool thing is that it also has NCache Express which is free for 2-server environments.

]]>