On Sat, 2002-04-27 at 04:54, Dave Watts wrote:
When should you use each? Right now, I do not use
named locks.
If you're using CF 4.5.x or higher, you should use the SCOPE attribute when
locking memory variables, and the NAME attribute for locking other things,
like CFX tags, if they
The problem with this is that you can't just lock part
of the APPLICATION scope for example, if you want to do
something to only some stuff stored in the app scope you
need to use named locks - but if you do that you're gonna
have to be careful that you don't use a name that some
other
- Original Message -
From: Dave Watts [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Monday, April 29, 2002 8:04 AM
Subject: RE: Locking by name - is is application independant ?
The problem with this is that you can't just lock part
of the APPLICATION scope for example
Is the goal in locking a CFX tag to prevent two users from
accessing the tag simultaneously? So if two applications use
the same CFX tag the tag should have the same lock name?
Yes, if the CFX tag needs to be locked. Not all CFX tags do; some are
thread-safe, others aren't.
Dave Watts,
If i have two applications on the same CF server, indentified
by to different CFAPPLICATION tags, say one with an
application name Foo and the other Bar, and I execute a bit
of code in each that does a *named* cflock using the same
name, will that lock extend across applications ?
It's
When should you use each? Right now, I do not use named locks.
ANdy
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 26, 2002 9:04 AM
To: CF-Talk
Subject: RE: Locking by name - is is application independant ?
If i have two applications on the same
When should you use each? Right now, I do not use
named locks.
If you're using CF 4.5.x or higher, you should use the SCOPE attribute when
locking memory variables, and the NAME attribute for locking other things,
like CFX tags, if they need to be locked.
If you're using CF 4.0.x, you don't
If you're using CF 4.5.x or higher, you should use the SCOPE
attribute when locking memory variables, and the NAME attribute
for locking other things, like CFX tags, if they need to be locked.
Is the goal in locking a CFX tag to prevent two users from accessing the
tag simultaneously? So if
8 matches
Mail list logo
