I apologize in advance if this has already been hashed and rehashed...
In the Web Application Construction Kit for CFMX, it says:
Previous versions of CF required you to use locks far more frequently,
even when there wasn't a race condition issue at hand. Basically, you
needed to lock every
2004 8:09 PM
To: CF-Talk
Subject: YALT: when to lock in CFMX
I apologize in advance if this has already been hashed and rehashed...
In the Web Application Construction Kit for CFMX, it says:
Previous versions of CF required you to use locks far more frequently,
even when there wasn't a race
I think that the last quote you show is a holdover from the old pre-MX
documentation.I asked this exact question to Ben F at the last Devcon
prior to MX's initial release (I guess that would be 3 cons ago), and his
unequivocal response was in agreement with the first 2 quotes you listed -
much to
-Original Message-
From: Conan Saunders [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 10, 2004 1:09 AM
To: CF-Talk
Subject: YALT: when to lock in CFMX
I apologize in advance if this has already been hashed and rehashed...
In the Web Application Construction Kit for CFMX, it says
I sent this a couple hours ago and haven't seen it show up on the
list yet, so I'm sending again.
Thanks Barney, Peter, and Reed for your responses.
After reading Barney's article, I still have one more question.
When you have a race condition on unlocked shared memory variables, what
are
),
not in CF or your application.
Cheers,
barneyb
-Original Message-
From: Conan Saunders [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 10, 2004 3:05 PM
To: CF-Talk
Subject: RE: YALT: when to lock in CFMX
I sent this a couple hours ago and haven't seen it show
up on the
list yet
6 matches
Mail list logo
