Manually locking all reads and writes (locking by scope) is good. Beware of things that might not look like writes - like a query with a name of application.queryname is actually a write into the application scope.
Also, use the Duplicate() function with CFSET whenever making a copy of a complex variable (arrays & structures, at least. Allaire/MM say queries are complex, other folks say they're not). If you don't use Duplicate() when copying complex variables your copy is a pointer to the original rather than a real copy. And test for session validity at the beginning of every request. best, Chris Norloff ---------- Original Message ---------------------------------- from: <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] date: Sun, 30 Sep 2001 17:30:46 -0700 >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. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com 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
