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.
When Session Variables Go Bad
About the author
Bruce Johnson
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.
VB 6 books
-
Dynamic Web Application Development with ASP.Net (Computing)
This is the latest book from Cengage Learning on "Dynamic Web Application Development with ASP.NET...
VB 6 forum discussion
-
CorelDRAW VBA: cdrTraceLineDrawing FAILS, producing single linear path instead of Centerline trace?
by dancemanj (0 replies)
-
client/server application using activex
by beautifulheart (0 replies)
-
gamedominoqiuqiuqq
by shielaariel888 (0 replies)
-
Problem viewing IIS website locally
by ep1 (0 replies)
-
System Error &H8007007E. The specifed module could not be found.
by swiftsafe (5 replies)
VB 6 podcasts
-
Hanselminutes: Startup Series: Buying an Existing Small Company or Online Application
Published 8 years ago, running time 0h34m
Scott talks to Rob Walling about how he purchases small niche products and companies online and revitalizes them. He recently purchased an existing product that consisted of a 300 gig database and tens of thousands of lines of Classic ASP. How did he know it was valuable? What's next?
Comments