I'll go along with this sentiment. Use session variables when you need them, but put what you can into the applicaiton and request scopes. RAM is cheap.
--Ferg Robert Everland III wrote: >I would reevaluate the session variables you have and see what variables never >change between users. I would then take those variables and move them to the >application scope. Any functions you are using I would move to the application >scope. I would NOT use client variables. The biggest bottleneck for your >application will be from the database to your application enviroment. Every >time you would need to read or write a variable would be a write to the >database. > > > >Bob Everland > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:223674 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
