About Cache

[Guest]

In application state, we need to use "Application.Lock()" before we write
something into Application["xxx"]. My question is do we need use
"Application.Lock()" to LOCK the cache before we write into Cache["xxx"]?

 

[Shiva]

No, not required.

In application state, we need to use "Application.Lock()" before we write
something into Application["xxx"]. My question is do we need use
"Application.Lock()" to LOCK the cache before we write into Cache["xxx"]?

 

[Guest]

someone can tell me why? How can asp.net keep synchronization without
Locking the cache?

 

[Saravana]

Its not required. Its thread-safe.

 

[Shiva]

Cache is thread-safe.

someone can tell me why? How can asp.net keep synchronization without
Locking the cache?

 

[bruce barker]

you don't strickly need it for application either, as the actually update is
thread safe. but if you use the following logic:

test if not in cache/application
build object
stick in chahe/application
else
return cache/object.

with out a lock before the test, two (or more) threads can detect the empty
state, both build the object, and both place their created objectes in the
cache (last one winning). a lock before the test will prevent the race.


-- bruce (sqlwork.com)



| In application state, we need to use "Application.Lock()" before we write
| something into Application["xxx"]. My question is do we need use
| "Application.Lock()" to LOCK the cache before we write into Cache["xxx"]?