I assume that the BO are actually synchronized with a db as well? If so, Rob Howard has some sample code [1] to invalidate the cache on a db update via a trigger-invoked callback. I'm sure it's modifiable to your requirements.
John [1] ASP.NET Cache Invalidation on Database Change, http://www.gotdotnet.com/team/rhoward/SQLDependency.zip For more info, see http://www.gotdotnet.com/team/rhoward/ > -----Original Message----- > From: Moderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED]] On Behalf Of > Alex Henderson > Sent: Thursday, June 27, 2002 7:09 AM > To: [EMAIL PROTECTED] > Subject: [ADVANCED-DOTNET] Synchronsing events caches across > web farms... > > > What's the best strategy for ensuring that cached data (i.e. > business layer objects you have cached for performance > reasons) are synchronized across multiple machines in a web farm? > > 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... Does this sound feasible, and are there performance > implications for hosting a "remoting" server within a web site? > > You can read messages from the Advanced DOTNET archive, > unsubscribe from Advanced DOTNET, or subscribe to other > DevelopMentor lists at http://discuss.develop.com. > You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
