it is better to wrap the whole hting inside the cflock
the reason? Because what if it was read an existing session variable from
another thread? See? wait, i dont know what I'm saying. dont listen to
me. argh
-Original Message-
From: Tim Bahlke [mailto:[EM
Should client variables such as the following be inside a ?
DELETE FROM CData
WHERE CFID = '#Cookie.CFID#:#Cookie.CFTOKEN#'
Will
--
[EMAIL PROTECTED] -=- www.lukrative.com
Local-Advertising -=- www.localbounty.com
> it is better to wrap
;t the attached
code a bad idea? I was given the impression that it's not a good idea to
monkey around manually with CFs client variable database.
Bob
-Original Message-
From: W Luke [mailto:[EMAIL PROTECTED]]
Sent: March 23, 2001 3:03 PM
To: CF-Talk
Subject: Re: session variable locki
> Should client variables such as the following be inside a ?
No. Only memory variables (session, application, server) need to be locked.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
~~
Str
I was wondering, is there somewhere I can find a good discussion on why
locking session variables is a good idea? I have heard that it is something
that should be done, but our project leader insists that we do not need to
do it. What are the pros and cons of locking session variables?
Chris Ma
CTED]>
Sent: Friday, March 23, 2001 5:41 PM
Subject: RE: session variable locking question
> I was wondering, is there somewhere I can find a good discussion on why
> locking session variables is a good idea? I have heard that it is
something
> that should be done, but our project lea
6 matches
Mail list logo
