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 am reading the article:
Nine Options for Managing Persistent User State in Your ASP.NET Application
by Steven A. Smith (Doesn’t he host a show on ESPN?)
In the article, Steven makes the following statement: “When dealing with a single ASP.NET page, ViewState is a better choice than QueryString for maintaining state”
Unfortunately, he does not explain why that is so. Why is this so?
I would imagine because the QueryString is part of the URI of the page – and thus can be tampered with by the user. Not to mention there’s a limited amount of space in the QueryString – limited to the maximum size of a URL (2048 bytes in IE, other browsers are more accommodating).
Aside from tampering, storing random bits of state in the QueryString would lead to very ugly URLs – and therefore URLs that are unfriendly to search engines.