> The one thing to watch out for is that since the CFC is in a > shared scope, it's instance data is also in a shared scope, > and therefore needs to be locked appropriately. There is a > debate as to whether that's better performed within the CFC
Sorry for the late response on this, but I wanted to be sure of one thing. Barney, you aren't saying that all uses of data needs to be locked, right? I guess I'm asking you to define "appropriately." Some people (based on life during the cf5 times) still say, "LOCK EVERYTHING OR DIE!", and certainly that is not the case anymore. You can have instance data in a persistant CFC that is NOT in danger of race conditions, and of course would not need to be locked. >Along the same lines, its VERY important to properly use the 'var' keyword in your This should be in the footer of every page in the cf documentation. ;) =========================================================================== Raymond Camden, ColdFusion Jedi Master for Mindseye, Inc (www.mindseye.com) Member of Team Macromedia (http://www.macromedia.com/go/teammacromedia) Email : [EMAIL PROTECTED] Blog : www.camdenfamily.com/morpheus/blog Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda ---------------------------------------------------------- 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 www.mail-archive.com/[EMAIL PROTECTED]
