Thank you, Fredrik.
Jason

>
> Subject: Re: Cache vs Application object
> From: "Fredrik Normén" <fnormen@h...>
> Date: Wed, 19 Dec 2001 08:59:49
> X-Message-Number: 1
>
> Hi,
>
> One instance of the Cache class is created per application domain, and it
> remains valid as long as the application domain remains active.
> You can't trust the Cache class to 100%, if you don't specifed a expire
> time for the cache item, you don't know when it will be expired. For
> example, when system memory becomes scarce, the cache automatically
> removes seldom used or unimportant items to allow memory to be used to
> process a high volume of requests. This technique is called scavenging.
> It is one of the ways that the cache ensures that data that is not
> current does not consume valuable server resources.
>
> The Application object will live until the last user leaves the
> application.
>
> /Fredrik Normén
>
> > Hi,
> > Can someone tell me the advantage of using the Application object vs.
> the
> > Cache?  Seems like the Cache has better fine-tuning with file
> dependencies,
> > expirations, and internal locking/unlocking.  Why would I need to use
> > Application object?
> > Thanks.
> > Jason