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
Can you explain architecture of your project ?
What is AutoPostback?
Which control has default post back is enabled(true)?
What is a windows service?
What is web configuration file and how to use in web application
What is session state server?
Describe Segmentation With Paging?
How do you implement sql caching in asp.net?
How do cookies work? Give an example of their abuse.
How to manage different kinds of sessions in ASP.NET?
What is is post back property in asp net?
Why Unload event of MasterPage Calls first in ASP.net ?
How does session authentication work?
Difference between application events and session events
What is mta?