If I update session state, should I lock it, too? Are concurrent accesses by mul

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?

Question Posted / kumar saurabh

1 Answers
1556 Views
I also Faced
E-Mail Answers

If I update session state, should I lock it, too? Are concurrent accesses by multiple requests execu..

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

Post New Answer

More ASP.NET Interview Questions

What methods are fired during the page load?

2 Answers

What is Runtime callable wrapper?

2 Answers

What is DTS package?

2 Answers Accenture, TCS,

What do you mean by authentication?

0 Answers

Suppose you display a data having 200 records in a datagrid. Then you edit 100 records of them. Now when you will press update button,all 100 records should be updated in single shot rather than reading every record and updating. How to do it?

4 Answers Wipro,

Explain the different types of directives in .net?

0 Answers

Why is global asax is used?

0 Answers

Can you explain one critical mapping?

0 Answers

How Clustered Index and Non clustered index stored on SQL server?

2 Answers TCS,

1.can we add connection string in global.asax?????????? 2.what are the default files included when we create new web application????

7 Answers Sparsh,

What is the use of directives & explain with example?

2 Answers C Squared Systems,

Define viewstate in .net?

0 Answers

For more ASP.NET Interview Questions Click Here