2

It is my understand that the ASP.NET Cache is part of the w3wp process, meaning writing to and reading from it

  • does not cross process boundaries
  • does not require marshalling
  • does not require or perform serialization of objects placed in it

(All in comparison to using ASP.NET Session State Server which does all these things)

Is this correct?

Alex
  • 75,813
  • 86
  • 255
  • 348
  • 1
    If you are refering to the single HttpApplicationState which is created for each asp.net app then yes, the storage is a primative in memory collection, and doesn't have a provider model like session state that may mean marshalling / serialization. – meandmycode Oct 01 '09 at 22:51
  • @meandmycode Good info, but I do not think Alex refers to the HttpApplicationState class. Do you, Alex? – o.k.w Oct 02 '09 at 00:15
  • @okw/meandmycode: I'm referring to the object that comes with the HttpContext (HttpContext.Current.Cache). – Alex Oct 02 '09 at 00:40

1 Answers1

1

If you are refering to HttpContext.Current.Cache, then it will be part of the w3wp process. Caching of this form is stored in memory and do not require serialization.

It should not cross process boundaries, it will be a disaster if it does. That goes for marshalling too.

o.k.w
  • 25,490
  • 6
  • 66
  • 63