There is also an issue if you have several servers. Session variables are not really a good use... for it is only being stored on one server and won't be available on the other server. And the best option here is either use a Cookie or a Client variable.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Sunday, September 30, 2001 5:31 PM To: CF-Talk Subject: Points of failure for session variables Of course I've used system variables several times in the past, but never in an application where their proper functioning is absolutely necessary, until now. The application I'm building now relies heavily on session variables and will fail if variables are not properly passed. Of course, I'm using CFLock around all session variables (both read and write). Besides that, I'm wondering are their other problems to look and plan for? Is it possible that session variables will not work with some clients? If so, under what conditions. How do you plan for such possible failures? I just want to do my best to cover all of the bases here. H. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
