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
In a webservice, need to display 10 rows from a table. Which is the best choice among datareader or dataset?
What are Caching techniques in .NET
Can you explain one critical mapping? Performance issue which one is better?
Explain the various authentication mechanisms in asp.net.
What is the difference between typeof() vs gettype()?
I have an external link in my application say www.xyztest.com. Today this site works on http protocal. Tommorow it may run on https. So i cant hardcore the protocal in the site. When a user clicks on the link how can i know if the external site works on http or https and takes him to that place?
What are sessions and cookies?
What are custom user controls in asp.net?
What is difference between ispostback and autopostback in asp net?
What is the difference between client-side and server-side validations in ASP.NET?
What is difference between cookies and cache?
What is custom events?
How can we call webservices in Banking Applications? and where we are using it?
Which is better viewstate or session?
How to prevent client side validation from the ASP.NET validation controls?