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

What Are Different Types of Debbugers

2 Answers Accenture, TCS, Wipro,

What are the Application_Start and Session_Start subroutines used for?

5 Answers Siebel Systems,

Will the asp.net validators run in server side or client side? How do you do client-side validation in .net? How to disable validator control by client side javascript?

0 Answers

how to update data using store procedure

1 Answers

WHAT IS THE SEQUENCE IN WHICH ASP.NET EVENTS IS PROCEED?

4 Answers

Have you used microsoft dataaccess blocks and Exception blocks?

1 Answers Microsoft,

What is cached data phone?

0 Answers

In Code-Behind class which kind of code (server or client) is found ?

0 Answers Siebel,

What setting must be added in the configuration file to deny a particular user from accessing the secured resources?