So in this case, the lock is for performance reasons? Does that still qualify as a race condition? (Which I thought was only to prevent data corruption.) I know this is nit picky - but I'm just curious.
======================================================================== === 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 > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Sean A Corfield > Sent: Thursday, May 29, 2003 2:44 PM > To: [EMAIL PROTECTED] > Subject: Re: [CFCDev] CFCs in memory > > > On Thursday, May 29, 2003, at 06:42 US/Pacific, Raymond Camden wrote: > > I'm curious why you advocated the use of cflock here? I didn't read > > his original message, only the part your quoted, but it sounds like > > all he is doing is reading in config data, static type data. > > He is setting an application variable and there is > (presumably) quite a > bit of overhead involved in creating the CFC - it reads from a config > file etc - so the lock is simply 'best practice' to ensure the > initialization doesn't occur twice and, in particular, doesn't occur > twice at the same time! > > Sean A Corfield -- http://www.corfield.org/blog/ > ---------------------------------------------------------- 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).
