When Session Variables Go Bad

Introduction

So you've heard the stories about how bad it is to use Session variables in an ASP application. In the newgroups, 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.

You might also like...

Comments

About the author

Bruce Johnson Canada

I am the owner of a small application development consulting company that specialized in the design and implementation of Internet-based applications. While there are others who can make a web ...

Interested in writing for us? Find out more.

Contribute

Why not write for us? Or you could submit an event or a user group in your area. Alternatively just tell us what you think!

Our tools

We've got automatic conversion tools to convert C# to VB.NET, VB.NET to C#. Also you can compress javascript and compress css and generate sql connection strings.

“Perl - The only language that looks the same before and after RSA encryption.” - Keith Bostic