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
1638 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

Why do you use the app_code folder in asp.net?

0 Answers

What is a SESSION and APPLICATION object?

0 Answers

In what order do the events of an ASPX page execute. As a developer, why is it important to understand these events?

5 Answers Syntax Softtech, TCS,

What’s the difference between asp.net web forms and asp.net mvc?