Do I really need to build a custom caching engine?

[thedotnetarchitect]

To keep the background simple here is my problem, I have two web
servers in a web farm I would like to have a centralized caching system
on another server, where I can add and remove items from cache from
that one central server, the other two web server will share the cached
data from this server such as serializable business objects and data
objects. I would like the storage system to be SQL server and the data
that is shared from the cache is not session specific but the cache
data is accessible to all session running on either server. Is this
possible now or do I need to build a custom caching engine based on sql
server that these to web server can access to render data to any and
all users.

 

[sloan]

http://spaces.msn.com/sholliday/ 9/27/2005

and the article I reference in the blog:
http://secretgeek.net/QAD_Remoting.asp

namely
#3 under "why use .net remoting"

...

If you need a super object holder, persistent among all servers among a web
farm, I would suggest the remoting server approach.