Another CF4.0-only question... Jeez, I feel like I'm back in the stone
age doing this with MX flying around!
What's the deal with locking shared scope variabled in CF4.0, which
doesn't support the SCOPE attribute for CFLOCK? Instead of:
cflock scope=APPLICATION type=READONLY timeout=10
temp
What's the deal with locking shared scope variabled in CF4.0,
which doesn't support the SCOPE attribute for CFLOCK? Instead of:
cflock scope=APPLICATION type=READONLY timeout=10
temp = application.variable;
/cflock
Should I use:
cflock type=READONLY timeout=10
temp =
, 2002 9:55 AM
To: CF-Talk
Subject: CF4.0 shared scope locking?
Another CF4.0-only question... Jeez, I feel like I'm back in the stone
age doing this with MX flying around!
What's the deal with locking shared scope variabled in CF4.0, which
doesn't support the SCOPE attribute for CFLOCK? Instead
.
/rob
-Original Message-
From: Rob Baxter [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 15, 2002 10:09 AM
To: CF-Talk
Subject: RE: CF4.0 shared scope locking?
You need to use the name attribute to specify a name unique to that locking
code. For example, for Session var locking I usually
On 5/15/02, Rob Baxter penned:
You need to use the name attribute to specify a name unique to that locking
code. For example, for Session var locking I usually used cflock
name=#CFID#_#CFTOKEN# ...
I don't think that's going to work as user A will have a different
cfid and cftoken than user B.
- Original Message -
From: Bud [EMAIL PROTECTED]
snip
To set a value in a variable named session.cart:
cflock name=#request.dsn#_basket timeout=10 type=exclusive
cfset session.cart.product_id = #form.product_id#
/cflock
To read session.cart:
cflock name=#request.dsn#_basket timeout=10
be completely independant of one another.
/rob
-Original Message-
From: Bud [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 15, 2002 10:48 AM
To: CF-Talk
Subject: RE: CF4.0 shared scope locking?
On 5/15/02, Rob Baxter penned:
You need to use the name attribute to specify a name unique
7 matches
Mail list logo
