And those of us still on 4.0x don't (I think) have that option.
-----Original Message-----
From: Peter Theobald [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 19, 2000 3:16 PM
To: CF-Talk
Subject: LOCKING revisited...
Ok, given that we all agree:
** Access to shared variables should *ALWAYS* be locked **
Then why on Earth shouldn't I just turn on Automatic Read Locking for
Application (and Session et al if I use them) scope and only worry about
write locking in my code?
Why doesn't everyone do that, with the rare exception of some code that has
unusual locking needs.
I've heard the argument that automatic read locking is a slight performance
hit. It couldn't be more of a hit than parsing <cflock> </cflock> around
every access and still doing the read lock anyway!
---------------------------------------------------------------------------
Peter Theobald, Chief Technology Officer
LiquidStreaming http://www.liquidstreaming.com
[EMAIL PROTECTED]
Phone 1.212.545.1232 x204 Fax 1.212.545.0938
To put this contact information into your Palm device, click here:
http://www.coola.com/cgi-bin/addinfo.cgi?pid=15803&rid=972879910&type=A
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
