Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Stateless Management Dilemma 1

Status
Not open for further replies.

MikeCole

Programmer
Jul 6, 2000
4
US
I am learning ASP by developing a Web application with MS SQL database maintenance capabilities.<br><br>I was successfully using Session variables to pass user inputted fields to other ASP pages.&nbsp;&nbsp;But, I understand that for a robust application using Session variables is not recommended.&nbsp;&nbsp;I read that hidden, cookies, querystring can also be used to pass fields to other pages.<br><br>I need some advice on what are the common practice out there in the Web application development world.&nbsp;&nbsp;<br><br>I would appreciate your feedback on this matter.&nbsp;&nbsp;&nbsp;<br><br>Mike<br><A HREF="mailto:appbussys_mjc@compuserve.com">appbussys_mjc@compuserve.com</A>
 
Dear Mike,<br><br>First of all do you need to be concerned with performance? What I mean is, what is your expected load on the application, unless you expect thousands of visitors per day using the session object should be strain on the server. The only way to be sure how much your design is effecting performance is to stress test the application. Check out the WCAT tool from MS... look here:<br><A HREF=" TARGET="_new"> <br><br>Then consider this as well. You can control the scope of the session object by creating IIS Applications. If you only need to use the session object for subset of your site then place those pages into their own application thus reducing the overall 'session' use on the server.<br><br>However if you are still concerned hidden form variables in combination with client and server side script can accomplish just about anything you want in regards to retaining data across multiple pages. <br><br>You can even simplify your code by creating classes in your server side code that will handle the persistence for you, but that's another issue entirely.<br><br>Hope this helps<br>-pete<br><br>
 
oops...<br><br>&gt; unless you expect thousands of visitors per day using the session object should be strain on the server.<br><br>should be:<br><br>unless you expect thousands of visitors per day using the session object should 'NOT' be a strain on the server.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top