root level so that all worker processes can access.
cache objects. And to clear all cache entires, I will change the timestamp of
"Alvin Bruney [MVP - ASP.NET]" wrote:
> You can implement a notification system that basically notifies all the
> cache objects in the garden to refresh themselves. I've seen this
> implemented, but it was prone to failure.
>
> If you architecture is that complicated, you need to move cache to a
> database or a queue system
>
> --
> Regards,
> Alvin Bruney - ASP.NET MVP
>
> [Shameless Author Plug]
> The Microsoft Office Web Components Black Book with .NET
> Now available @
www.lulu.com/owc > "mk" <mk@discussions.microsoft.com> wrote in message
> news:2C0DE4C6-C207-4F30-8446-82C3F8086CE7@microsoft.com...
> > if we configure an ASP.Net application pool with more than one worker
> > process
> > (web garden), they do not share session object, application object or
> > ASP.net
> > intrinsic cache object. If I want all these processes to share one single
> > cache, is it possible to configure at all some way or the other?
> >
> > My problem is I am using Application (HttpApplicationState) object for
> > caching. And if this not going to be shared across worker processes in an
> > application pool, then when I have to invalidate some entries in cache as
> > the
> > data is not valid any more, I cannot delete entries in all caches at one
> > time. Only the worker process that handled the request would clear its
> > cache
> > entries and the rest of the processes still have invalid data.
> >
> >
> >
> > What is the best way handling this scenario?
> >
> >
>
>