Sure, I inherited one.
It was a Customer Service application where the customer's unique
identification number was a session variable. The application made heavy
use of frames to split information along the lines of "current" and
"historical" activity.
Needless to say there were more than one CS rep using the application at the
time. Any time one of the reps entered in identification criteria while
another rep was using the Application caused the Application to fail.
But hey it worked great in development/test when just a single user was
using the Application.
Suggestion: No great need to tell them horror stories when you can show
them first-hand. Just crash the app in dev/test by having multiple people
challenge that portion of the code at the same time.
Lonny Eckert
Hesta Corporation
[EMAIL PROTECTED]
Hesta 610-230-2500 x147
-----Original Message-----
From: Don Vawter [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 06, 2001 10:11 AM
To: CF-Talk
Subject: Any horror stories from not locking session vars?
I have been asked to do a code review of a site and I have found that the
developers don't bother to lock session variables when then read or write
them. Does anybody have an good horror stories about the dangers of doing
this so I legitimately show the customer why this is a problem. He is a
nontechnical person so any talk of needing to single-thread processes when
using shared variables won't mean a thing to him. Since I always lock around
the variables I can't give him any personal horror stories. Perhaps some of
you have heard of some (I KNOW they won't come from YOUR sites because you
always follow best practices ;-) but maybe you inherited some.)
TIA
Don
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
