Hi,
There is a definite difference between the SCOPE and NAME attributes in
CFLOCK. When you use CFLOCK with the SCOPE attribute, the CF server will
only process one request at a time for that scope. Meaning that if two
different users, with different computers, are at a page where you use
CFLOCK SCOPE="application", even if the variables are different, only one
page request can access the application scope at a time, as if the second
request was waiting in line for the first one to finish.
When you use the NAME attributes, CF doesn't stop other requests for the
same scope, it stops requests for only other CFLOCK statements with the same
exact NAME attribute.
If you are using CFLOCK for session variables, you should use the SCOPE
attribute, so that there are not two different requests updating the session
variables at the same time.
-Brent
-----Original Message-----
From: Hamid Hossain [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 14, 2001 10:12 PM
To: CF-Talk
Subject: CFLOCK Scope vs Name attributes !!
Hi,
I am wondering if there is a real different for using
scope or name attribute with CFLOCK
<CFLOCK SCOPE="SESSION" ... >
or
<CFLOCK NAME="#SESSION.SessionID#" ... >
Regards,
Hamid Hossain
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
