Cache is faster. It has been tuned for performance and efficiency whereas
application is only presented for backward compatibility with asp classic.
Moving forward you should embrace cache instead of application strategies.
Regards

Signature
-----------
Got TidBits?
Get it here: www.networkip.net/tidbits
> What is faster, reading a saved DataSet from an Application.Get() or
> reading the same DataSet from HttpCache?
Either way you're just accessing a pointer which points to
the real DataSet object. But Application.Get() might be a
bit faster because HttpCache has to do some internal book
keeping work such as cache entry expiration date, etc.
>-----Original Message-----
>What is faster, reading a saved DataSet from an Application.Get() or
>reading the same DataSet from HttpCache?
>.
Alvin Bruney - 06 Dec 2003 01:01 GMT
No it's not, see my reply thread.

Signature
Regards,
Alvin Bruney
http://www.networkip.net/dotnet/tidbits/default.htm
> Either way you're just accessing a pointer which points to
> the real DataSet object. But Application.Get() might be a
[quoted text clipped - 6 lines]
> >reading the same DataSet from HttpCache?
> >.
Jerry III - 06 Dec 2003 10:43 GMT
Alvin's right, cache maintenance does not affect lookups - the expiration
time is not checked when you retrieve the object, that way it would never be
released if you never access it.
Jerry
> Either way you're just accessing a pointer which points to
> the real DataSet object. But Application.Get() might be a
[quoted text clipped - 6 lines]
> >reading the same DataSet from HttpCache?
> >.