> > You cited this example:
>
> > <cflock scope="SESSION" timeout="3"
type="READONLY">
> > <cfset session.clientBalance =
session.clientBalance - 99.50>
> > </cflock>
>
> No need to waste time there. I corrected it two days
ago.
No you didn't. You changed the lock to EXCLUSIVE. The fact
that the lock
is there *at all* is what's incorrect.
> I suppose what you mean is that, since version MX,
Coldfusion is thread-safe.
> Two threads will therefore not modify a variable at the
same time. As I said
> before, that is not an exact science.
Yeah. It is. Well so close to one that when one is operating
at the CF
level of things, it might as well be.
> Thread-safety is complicated by technical
> matters as atomicity and reentrancy. Note in particular
that <cfset
> session.clientBalance = session.clientBalance -
99.50> is a recursive statement.
[snort]
Nice sentence. Nice use of buzzwords. It doesn't *mean*
anything though,
does it?
> This
http://livedocs.macromedia.com/coldfusion/7/htmldocs/00001167.htm
> explains how and why to a single cfset.
The top section of that guidance is wrong. But fair enough if
that's what
you were running with: one *should* be able to trust the
docs.
The bit starting with "Ensuring consistency of multiple
variables" is
correct, though.
I will pursue a correction for the top bit.
--
Adam