Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Possible Duplicate:
ASP.NET Application state vs a Static object
I am using the static variable to share the data between all the users. But we have also application object, with help of the application , we can also share data between all user.
Can any explain, where can we use static variable and the application object.
Any of the Application object\static object approach would fail in a multi server scenario. If your state sharing is more of a read only view of some data things may work, but in a read-write scenario things would fail. In such a scenario you need delegate state storage to another machine altogether (such as state server, sql server, memcache etc).
If you compare static and application object i would strongly suggest you to go with Application object as it has some thread synchronization built into it, which can help avoid inconsistent data retrieval.