In an ASP.NET application you can store pretty much anything in the Session as long as you can handle the cost. What is the intended usage and what is most frowned upon when using the Session to store data?
Share
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.
In an ASP.NET application you can store pretty much anything in the Session as long as you can handle the cost. What is the intended usage and what is most frowned upon when using the Session to store data?
Any user specific data that has to be persistent across various pages of an application to the logged in user can stored in a session. The objects to be stored in Session need to be serializable.
Usually, it is recommended that the session should be used a little sparingly, because with an increase in number of concurrent users,the load on server memory increases and at one point, it recycles the memory causing all session data to be dumped. This causes a premature timeout of the session.