Exclusively lock all of your sets, and ReadOnly lock all of your reads
(references).
Just do it, it's not too tough. :)
Watch out for application variables too.
Jamie
On Tue, 08 May 2001 11:15:20 -0700, "Gregory Harris"
<[EMAIL PROTECTED]> wrote:
>Ok, what is the consequence for failing to lock a session variable? Right now it
appears that with some unlocked session variables that we have on an application
that we inherited, it appears to be generating some huge memory leaks in ColdFusion
whenever we're going through the application. Is it possible the 2 are related?
Also what is the best locking scope for a session variable. ReadOnly or a Named
Exclusive?
>
>Gregory Harris
>Web Developer
>____________
>The Stirling Bridge Group, LLC
>*We Engineer Internet Business Solutions*
>TEL: (949) 707-1534 FAX: (949) 707-1535
>
>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
