Application state vs. Cache API

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Daniel Walzenbach - 10 Jul 2004 04:32 GMT

Hi,

I need to cache infrequently changed data used by the entire application.
Does anybody know whether using Application state
(Application["YourGlobalState"] = somevalue;) or the Cache API
(Cache.Insert) is more preferable?

Thanks a lot

Daniel

Reply to this Message

Scott Allen - 10 Jul 2004 06:59 GMT

The cache object is more flexible in the long run. You can set a
duration and a priority for the cached item, for instance.

--
Scott
http://www.OdeToCode.com

>Hi,
>
[quoted text clipped - 6 lines]
>
> Daniel

Reply to this Message

Paul Glavich [MVP - ASP.NET] - 10 Jul 2004 09:38 GMT

The cache is good, but it is considered volatile. There is never any
guarantee that the data is there. The item may be removed when it expires or
some condition is met (something you explicitly set), or the runtime may
remove the item when memory gets low. In contrast, the application variables
are there for the duration of the applications life, unless explicitly
removed by you and it provides methods to synchronise access to the
varibales as well. (.Lock for example).

Signature

- Paul Glavich
Microsoft MVP - ASP.NET

> The cache object is more flexible in the long run. You can set a
> duration and a priority for the cached item, for instance.
[quoted text clipped - 13 lines]
> >
> > Daniel

Reply to this Message

Harry Simpson - 26 Aug 2004 16:37 GMT

True but as with all caching, one ALWAYS checks to see if the data is in the
cache and if not gets fresh data. So unless connection is iffy, this really
should be a concern.

Harry

> The cache is good, but it is considered volatile. There is never any
> guarantee that the data is there. The item may be removed when it expires
[quoted text clipped - 24 lines]
>> >
>> > Daniel

Reply to this Message

Application state vs. Cache API

Free Magazines