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 / 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 |
Explain method to handle error using HttpError in Web API?
What is the importance of Global.asax in ASP.NET?
What is ispostback method in asp.net? Why do we use that?
When web.config is called ?
What are the different authentication modes in the .NET environment?
Please brief not about xsd,xslt & xml?
What is asp.net web application?
Difference between response.redirect and server.transfer?
Explain the difference between web user control and web custom control?
What is the difference between session.abandon() vs clear()?
What is the request flow used for asp.net mvc framework? : asp.net mvc
To match the two different controls which control would we use ?
Visual Basic (800)
C Sharp (3816)
ASP.NET (3180)
VB.NET (461)
COM+ (79)
ADO.NET (717)
IIS (369)
MTS (11)
Crystal Reports (81)
BizTalk (89)
Dot Net (2435)
Exchange Server (362)
SharePoint (720)
WCF (340)
MS Office Microsoft (6963)
LINQ Language-Integrated Query (317)
WPF (371)
TypeScript (144)
Microsoft Related AllOther (311)