Interested to Buy Any Domain ? << Click Here >> for more details...
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?
- 1 Answers
- 1588 Views
- I also Faced
- E-Mail Answers
Answer Posted / 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 View All Answers
Why do we use datasource in asp.net?
Why do we use web config?
Which library is used by the testers and developers to develop automated tests and create testing tools?
What is advantage of asp.net?
What is the life cycle of an asp.net page?
Explain Authentication mechanism in dotnet
What are server activated objects?
Explain the reason why the javascript validation not run on the asp.net button but run successfully on the html button?
Can we use html in asp.net?
What is the difference between session and application?
Explain the function of new view engine in asp.net? : asp.net mvc
How can we pass info between 2 asp.net pages?
Where would you use an ihttpmodule, and what are the limitations of any?
Explain page output caching?
Which is faster union or union all?
