Somewhat related: is there any reason to do locking when you're only
*reading* from application variables?
> -----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/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
