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
- 944 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
How is it possible for .NET to support many languages?
What is the function of the ViewState property?
What is the difference between asp.net mvc and asp.net webforms? : asp.net mvc
What is difference between web api and web services?
Explain how do you validate the controls in an asp .net page?
Explain how viewstate is being formed?
What is ascx?
What are the two properties that are common on every validation control?
Elaborate differentiation between ViewState and SessionState?
14. What are your Future Plans for Swatz Oils GROUP U.K?
What is syntax code to send email from an asp.net application?
To redirect the user to another page which method do we use without performing a round trip to the client?
What are the steps to follow to host a web application on a web server?
Describe Segmentation With Paging?
Why do we need Sessions?
