The scope="" is optional as you can use the same locking syntax as in
4.0, ie. named locks (scope and name are mutually exclusive though, so don't
try both).
I'm running 4.5.2 ENT (and a 4.5 Pro) (so if it's a 4.5.1 bug I wouldn't
know) w/ strict attribute validation and it's working fine. I don't think
Allaire would cut their own throats by being that backwards incompatible; I
mean they provide deprecated functions like parameterExists() still, which
is a pre 4.x function.
So a cflock like this:
<cflock name="foobar" timeout="5">
Should work the exact same in CF4.0x and 4.5.x, if it isn't I think I'd
contact Allaire on the issue.
Hope it helps,
Raymond B.
Hrmm... interesting if it is something wrong w/ 4.5.1, as that could pose
some problems w/ quite a few commercial apps.
-----Original Message-----
From: Gene Kraybill [mailto:[EMAIL PROTECTED]]
Sent: January 22, 2001 17:31
To: CF-Talk
Subject: CFLOCK for 4.0.1 AND 4.5.1
I'm struggling with implementing CFLOCK so it runs on BOTH CF 4.0.1 and
4.5.1. (The
4.5.1 server has FULL CHECKING on.)
Given that 4.0.1 FORBIDS the SCOPE parameter in CFLOCK and 4.5.1 REQUIRES
it,
I thought I'd do a check for which version of CF was running and stash the
appropriate
CFLOCK parameters into a local variable. For example, if CF 4.5.1 or better,
I'd set the
parameter var to be equal to 'SCOPE="Application" TYPE="Exclusive"', etc.
So my CFLOCK would look like this:
<CFLOCK #VersionSpecificParameter#>
code...>
</CFLOCK>
But... CF throws an error on the pound sign, apparently not allowing the
specification
of parameters via variable.
Any ideas besides repeating the entire CFLOCK block for each version?
Gene Kraybill
---------------------------------
Gene Kraybill
LPW & Associates LLC
www.lpw.net
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
