Your lock only applies for the duration of the execution of code between the cflock tags. So if your second method call happens elsewhere, that portion of code will not be locked.
Cheers, Stace -----Original Message----- From: Magnus Wege [mailto:[EMAIL PROTECTED] Sent: Monday, November 22, 2004 12:22 PM To: [EMAIL PROTECTED] Subject: [CFCDev] CFCs locking when writing properties by setter-methods? Hi, I have just a simple question about locking von shared scoped objects, e.g. session.oOrder The object was previously locked when created by the CFC's init() method. When I call the setMethod(property), do I have to lock this setting by <cflock> again? Thanks for any replies to this "stupid" newbie question.... Magnus ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words '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 [EMAIL PROTECTED] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words '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 [EMAIL PROTECTED]
