In MX you only have to lock to prevent race conditions. Check the archive for more info.
-----Original Message----- From: Cohen, Michael [SMTP:[EMAIL PROTECTED] Sent: Thursday, September 18, 2003 2:18 PM To: '[EMAIL PROTECTED] ' Subject: [CFCDev] OT: Locking This may sound stupid but did I read somewhere that it *really* wasn't necessary to lock writes to shared scope variables in MX? That seems impossible to me but... Also, assuming you do have to lock writes, is it preferable to use the name attribute rather than scope? And if so, what is the behavior? Is it that the lock only affects other locks with the identical name? And that you should use different lock names if you are writing to different variables? For instance, <!---lock one session variable----> <cflock name="session.UserID" type="exclusive" timeout="10"> <cfset session.UserID = someValue /> </cflock> <!---on another page----> <cflock name="session.Cart" type="exclusive" timeout"10"> <cfset session.Cart = aStructure /> </cflock> Would these locks have no bearing on each other? i.e. two threads could hit each piece of code at exactly the same time and both would execute immediately? And is this best practice, that you use different lock names if you're writing to different variables? And this is more efficient than using the scope attribute because something like scope="session" would needlessly lock everything in the session scope? ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
