If you're relying on cookies to implement session variables, then there are a lot of ways that cookies can be blocked or otherwise not passed from server to client or vise versa. Hardware firewalls, software firewalls, proxy servers, browser settings are a few. Then there are issues at the server end... clustering, load balancing.
Jim ----- Original Message ----- From: <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Sunday, September 30, 2001 6:30 PM 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
