had they done that,
it likely would have placed a lock around each individual use.
which would have been hard on performance.
as they left it,
you control what to lock, which allows you to place a single lock around a
block of code.
-----Original Message-----
From: Dennis Powers [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 09, 2001 9:07 AM
To: CF-Talk
Subject: RE: I don't understand session locking :(
Maybe I am being a curmudgeon today, but it seems to me that if you ALWAYS
need to lock session and application variables and would never want to use
them without locks then Allaire should have coded that function into it's
core design.
Dennis Powers
UXB Internet
(203)879-2844
http://www.uxbinfo.com/
-----Original Message-----
From: Dave Watts [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 06, 2001 7:14 PM
To: CF-Talk
Subject: RE: I don't understand session locking :(
Yes, you need to place a lock around any reads or writes of Session
variables. If you don't lock reads as well as writes, and there's any
possibility of the two operations happening simultaneously (and there
usually is), then the lock you put on the write is useless by itself.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
