So you've heard the stories about how bad it is to use Session variables in an ASP application. In the news groups, one of the more frequent topics deals with the saving of state in a Web application. Specifically, comparing the ease of use and speed of Session variables versus the overhead of using a database or the awkwardness of hidden fields or query strings. Unfortunately, the simplicity of Session variables comes at the cost of scalability. But is that enough of a reason to ignore them completely? The purpose of the article is to examine the pros and cons of Session variables and provide suggestions that you can apply to your own situation.