s_sana
05 Feb 2007, 08:38 AM
Start using a distributed cache or an OutProc cache in your existing Enterprise Library 2.0 Caching Application Block (CAB) based applications without any code change. Just change your application's configuration file to plug-in NCache as your cache provider.
CAB provides a simple stand-alone InProc cache out of the box. However, your ASP.NET application worker process keeps recycling and each time it does that you lose all the in-memory cache and have to rebuild it. And, if you have multiple worker processes running on the same server then you have multiple copies of the cache that takes more memory and can also go out of sync with each other. What you really need is an OutProc cache to be used with CAB in these situations.
Additionally, if your ASP.NET application is running in a web farm, then you must have a distributed cache which CAB does not provide out of box. However, you can plug in NCache seemlessly and start using a distributed cache with CAB.
Whichever way you look at it, NCache gives you a much more feature-rich cache for CAB regardless of whether your application is running on a single server or a web farm.
Read more about NCache 3.1
http://www.alachisoft.com/rp.php?source=/webdevforums.com.news5/dest=/ncache/index.html
Download NCache 3.1
http://www.alachisoft.com/rp.php?source=/webdevforums.com.news5/dest=/download.html
CAB provides a simple stand-alone InProc cache out of the box. However, your ASP.NET application worker process keeps recycling and each time it does that you lose all the in-memory cache and have to rebuild it. And, if you have multiple worker processes running on the same server then you have multiple copies of the cache that takes more memory and can also go out of sync with each other. What you really need is an OutProc cache to be used with CAB in these situations.
Additionally, if your ASP.NET application is running in a web farm, then you must have a distributed cache which CAB does not provide out of box. However, you can plug in NCache seemlessly and start using a distributed cache with CAB.
Whichever way you look at it, NCache gives you a much more feature-rich cache for CAB regardless of whether your application is running on a single server or a web farm.
Read more about NCache 3.1
http://www.alachisoft.com/rp.php?source=/webdevforums.com.news5/dest=/ncache/index.html
Download NCache 3.1
http://www.alachisoft.com/rp.php?source=/webdevforums.com.news5/dest=/download.html