Alex, >It's an ASP.Net based website - so currently I'm think that perhaps we could >use remoting to force the caches on all machines to repopulate when a change >occurs on one web server...
I'd add a couple of questions more on that topic: "And what if some of the machines failed to 'repopulate' (or let me say 'reconfigure' here)? Ingnore? Retry? Abort?" "What guaranties that your entire Web farm is in consistent (predictable) state after the 'repopulation' was ordered or even finished?" I think the problem is real interesting if it's to be solved once and forever. stef You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
