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?
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
Explain Life cycle of ASP.NET page when a request is made.
Describe session handling in a webfarm?
What are the ways to show data grid inside a data grid for a master details type of tables? If we write any code for DataGrid methods, what is the access specifier used for that methods in the code behind file and why?
List some of the important session state modes of asp.net.
What is the mvc framework?
In which event of page cycle is the viewstate available?
Can I stream live content/events?
What are the 3 types of web?
What is the asp.net mvc folder conventions? : asp.net mvc
What is httpresponse?
What are themes and skins in 2.0, explain usage scenario?
How to disable cut, copy and paste in TextBox using jQuery in asp.net?
What are the security types in asp.net?
Contrast OOP and SOA. What are tenets of each ?
What is server components?