Good point. What about the CFC itself handling any locking? Would it make more sense in there then 'on the outside'? My gut feelings say the CFC should do all the work for me.
Well, yes, it would be nice to know that the CFC is multi-thread safe but that doesn't actually solve the "initialize only once" problem, which is what the if/lock/if does... If your locking is inside the CFC, you've already had to initialize it before the code inside can deal with locking... so it would only trigger if you actually initialized it more than once at the same time... which is what we're trying to avoid!
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
----------------------------------------------------------
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).
