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.
I’ve worked on several .coms and we’ve never used the built-in ASP.NET session state. It has always been check a cookie for a valid session checks and the session is compared to what’s in the DB or other means but ultimately it’s the cookie. We haven’t used any ASP.NET based session objects.
So why are people using all this session state server crap with MVC? I have never seen a need for it.
Me too. I never use ASP.NET session state in my web applications. I prefer designing them in a RESTful manner rather than introducing state. One of the very first things I do in any web application is to add the following line in web.config to ensure that any future developers don’t make the mistake of using session:
I guess people are using it to simplify the storage of some volatile data across multiple requests.