If I update session state, should I lock it, too? Are concurrent accesses by mul

If I update session state, should I lock it, too? Are concurrent accesses by multiple requests executing on multiple threads a concern with session state?

Question Posted / kumar saurabh

1 Answers
1650 Views
I also Faced
E-Mail Answers

If I update session state, should I lock it, too? Are concurrent accesses by multiple requests execu..

Answer / kumar saurabh

Concurrent accesses aren't an issue with session state, for two reasons. One, it's unlikely that two requests from the same user will overlap. Two, if they do overlap, ASP.NET locks down session state during request processing so that two threads can't touch it at once. Session state is locked down when the HttpApplication instance that's processing the request fires an AcquireRequestState event and unlocked when it fires a ReleaseRequestState event.

Is This Answer Correct ?

0 Yes

0 No

Post New Answer

More ASP.NET Interview Questions

web farm .. how does session shuld be stored... if inproc used? does the session persists from one server to other.

2 Answers TCS,

What does AspCompat="true" mean and when should I use it?

1 Answers Infogain,

What is a global postback url?

0 Answers

What is difference between view state and session state?