RE: CFLOCK Scope vs Name attributes !!

[Jay Sudowski - Handy Networks LLC]

Hamid,

If you are using a session variable as your cflock name, I'd imagine
that you are pretty much defeating the purpose of CFLOCK.  You'd have to
CFLOCK the CFLOCK ...

As for your question, here's info directly from the CF docs ...

SCOPE
Optional. Specifies the scope as one of the following: Application,
Server, or Session. This attribute is mutually exclusive with the NAME
attribute. See the Scope section for valuable information (Whenever you
display, set, or update variables, in one of the shared scopes, use the
SCOPE attribute to identify the scope as Server, Application or Session)

NAME
Optional. Specifies the name of the lock. Only one request will be able
to execute inside a CFLOCK tag with a given name. Therefore, providing
the NAME attribute allows for synchronizing access to the same resources
from different parts of an application. Lock names are global to a
ColdFusion server. They are shared between applications and user
sessions, but not across clustered servers. This attribute is mutually
exclusive with the SCOPE attribute. Therefore, do not specify the SCOPE
attribute and the NAME attribute in the same tag. Note that the value of
NAME cannot be an empty string.

Hope this helps ...

Jay
-----Original Message-----
From: Hamid Hossain [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, August 15, 2001 1:12 AM
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/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists