]]
Sent: 04 October 2002 22:53
To: CF-Talk
Subject: Re: Variable locking
On Friday, Oct 4, 2002, at 12:07 US/Pacific, Gaulin, Mark wrote:
Actually, that using NAME is not a better practice... the SCOPE
attribute is
safer and is also what MM support advised us to use (when applicable).
Pre-MX
On Monday, Oct 7, 2002, at 01:38 US/Pacific, Kola Oyedeji wrote:
I'm joining this thread late. Can I just confirm what you guys are
saying: In CFMX named locks should be used in place of scoped locks and
locks are only needed When a possible race condition could occur?
The last part is
For session scope, you need a name that is unique
to your session which may be harder to invent (you
could perhaps use a user ID if it exists or a per-
session UUID).
If I recall correctly, the MM recommended naming scheme for CF 4.01 would
work fine here - use the concatenation of CFID
For session scope, you need a name that is unique
to your session which may be harder to invent (you
could perhaps use a user ID if it exists or a per-
session UUID).
If I recall correctly, the MM recommended naming scheme for
CF 4.01 would
work fine here - use the concatenation
I have a question on Session variables. If I have a statement like
cfoutput#Session.Fullname#/cfoutput
do I need to use cflock tags with it?
thanks,
Luis
~|
Archives:
cfset session.fullname = variables.fullname
/cflock
Hope this helps!
Paul Giesenhagen
QuillDesign
- Original Message -
From: Luis Lebron [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Friday, October 04, 2002 1:16 PM
Subject: Variable locking
I have a question on Session variables
Lebron [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 04, 2002 2:17 PM
To: CF-Talk
Subject: Variable locking
I have a question on Session variables. If I have a statement like
cfoutput#Session.Fullname#/cfoutput
do I need to use cflock tags with it?
thanks,
Luis
On Friday, Oct 4, 2002, at 11:37 US/Pacific, Paul Giesenhagen wrote:
Yup (on CF5, good practice on CFMX but not required)
cflock timeout=20 throwontimeout=No type=READONLY
scope=SESSION
cfoutput#session.fullname#/cfoutput
/cflock
Better practice:
cflock timeout=20 throwontimeout=No
. NAME still has a place though, since there
are other kinds of locking you may need to do that SCOPE is inappropriate
for.
Mark
-Original Message-
From: Sean A Corfield [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 04, 2002 2:46 PM
To: CF-Talk
Subject: Re: Variable locking
On Friday, Oct 4, 2002, at 11:37 US/Pacific, Paul
Giesenhagen wrote:
Yup (on CF5, good practice on CFMX but not required)
cflock timeout=20 throwontimeout=No type=READONLY
scope=SESSION
cfoutput#session.fullname#/cfoutput
/cflock
Better practice:
cflock timeout=20 throwontimeout=No
Actually, that using NAME is not a better practice...
the SCOPE attribute is safer and is also what MM support
advised us to use (when applicable).
This is true for versions prior to CF MX. For those versions, you should use
the SCOPE attribute. Sean's point is only applicable to CF MX, in
On Friday, Oct 4, 2002, at 14:27 US/Pacific, Dave Watts wrote:
This is true for versions prior to CF MX. For those versions, you
should use
the SCOPE attribute. Sean's point is only applicable to CF MX, in
which you
only lock to prevent logical errors - in that case, you want your lock
On Friday, Oct 4, 2002, at 12:07 US/Pacific, Gaulin, Mark wrote:
Actually, that using NAME is not a better practice... the SCOPE
attribute is
safer and is also what MM support advised us to use (when applicable).
Pre-MX.
Sure, the scope of a NAME-based lock will be tighter than using
]
- Original Message -
From: Luis Lebron [EMAIL PROTECTED]
Newsgroups: cf-talk
Sent: Friday, October 04, 2002 2:16 PM
Subject: Variable locking
I have a question on Session variables. If I have a statement like
cfoutput#Session.Fullname#/cfoutput
do I need to use cflock tags with it?
thanks
I've been looking up information on cflock and cftransaction lately, I'm sad
to say that I haven't had any experience using them in the past. Am I
correct in saying that as a best practice cflock should always be used when
you're accessing or modifying variables in Session, Application, or Server
: Pablo Nevares [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 24, 2002 2:56 PM
To: CF-Talk
Subject: variable locking and transactions
I've been looking up information on cflock and cftransaction lately, I'm
sad
to say that I haven't had any experience using them in the past. Am I
correct
To: CF-Talk
Subject: RE: variable locking and transactions
here you go, it was given to me Monday from this listdave whiterod I
think ;)
You may find the following link useful:
ColdFusion Server (Versions 5 and Prior): ColdFusion Locking Best
Practices
TechNote 20370
http
ssion variable from
another thread? See? wait, i dont know what I'm saying. dont listen to
me. argh
-Original Message-
From: Tim Bahlke [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 22, 2001 2:15 PM
To: CF-Talk
Subject: session variable locking question
In the following cod
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
In the following code, do I need a lock around the entire cfif statement?
cfif IsDefined("Session.user")
cflock scope="Session" type="ReadOnly" timeout="5"
CFSET REQUEST.USER = Session.user
/cflock
/cfif
Is it better to declare [lock]cfparam name="Session.user"
ing 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:[EMAIL PROTECTED]]
Sent: Thursday, March 22, 2001 2:15 PM
To: CF-Talk
Subject: session variable locking question
In the following code,
24 matches
Mail list logo
