Not to digress into arguably useless discussions, but the note below reminded me why I took such offense to people coming up with rules like "you must always lock shared variable scopes" in the pre-CFMX days. All those people who memorized that rule are now confused with CFMX because there is no rule. If people had taken the time to explain why locking needed to happen then people would be better prepared to handle the situation with CFMX, which of course now requires people understand when and where to lock.

-Matt

On Wednesday, December 3, 2003, at 03:01 PM, Brian Kotek wrote:

Ray, I must admit that I am one of the people from the "old days" who is
somewhat confused about what/how to lock things in CFMX, especially when
it comes to CFC's persisted in the session or application scope. My gut
instinct is still to lock everything. Without asking you to write a
tome, can you (or Sean or Matt or anyone who knows) boil it down to a
few bullet points or tips? What needs to be locked and what can be left
unlocked, under what conditions?


Thanks,

Brian


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Raymond Camden
Sent: Wednesday, December 03, 2003 2:50 PM
To: [EMAIL PROTECTED]
Subject: RE: [CFCDev] Basic CFC Design Question

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.

---------------------------------------------------------- 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]


Matt Liotta
President & CEO
Montara Software, Inc.
http://www.MontaraSoftware.com
(888) 408-0900 x901


----------------------------------------------------------
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]

Reply via email to