Bruce:
Are you positive you are not thinking of HttpContext.Items?
The Cache is around for the duration of the application domain, the
Items collection is around just for the request.
--
Scott
http://www.OdeToCode.com
On Fri, 9 Jul 2004 09:14:48 -0700, "bruce barker"
<no***********@safeco.com> wrote:
HttpContext.Cache is tried to the request not the application or session.
Its created at start of request and destroyed at end. it supplies a way for
code and http modules to pass request data around.
-- bruce (sqlwork.com)
"James" <james@spam_.com> wrote in message
news:OL**************@TK2MSFTNGP09.phx.gbl... If I have set the session state for an asp.net application to be out of
process how does this affect the HttpContext.Cache? What I want to know it
is possible to store the Cache out of process as well?
Because I read in MSDN that:
One instance of this class is created per application domain, and it
remains valid as long as the application domain remains active. Information about
an instance of this class is available through the Cache property of the
HttpContext object or the Cache property of the Page object.