Should client variables such as the following be inside a cflock?
CFIF DateDiff("n", Client.LastVisit, Now()) GTE 360
CFQUERY NAME="delClientVars" DATASOURCE="localads" MAXROWS=1
DELETE FROM CData
WHERE CFID = '#Cookie.CFID#:#Cookie.CFTOKEN#'
/CFQUERY
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 locking question
Should
Should client variables such as the following be inside a cflock?
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
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
rch 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 leader insists that we do not n
it is better to wrap the whole hting inside the cflock
cflock scope="Session" type="ReadOnly" timeout="5"
cfif IsDefined("Session.user")
CFSET REQUEST.USER = Session.user
/cfif
/cflock
the reason? Because what if it was read an existing session variable from
another
6 matches
Mail list logo
