No locking is needed for the REQUEST scope.
-Original Message-
From: Tilbrook, Peter [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 22, 2003 6:09 PM
To: CF-Talk
Subject: Locking question?
Do I need to LOCK variables (when setting or reading)variables in the
REQUEST scope - particula
Nope. Just Session, Server and Application scopes.
> -Original Message-
> From: Tilbrook, Peter [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 22, 2003 6:09 PM
> To: CF-Talk
> Subject: Locking question?
>
>
> Do I need to LOCK variables (when setting or reading)variables in the
>
You can lock them all as a group.
Cheers,
Jeff Garza
Webmaster,
Spectrum Astro, Inc.
[EMAIL PROTECTED]
-Original Message-
From: Alii Design
To: CF-Talk
Sent: 6/2/01 8:18 AM
Subject: locking question
Do you need to lock each session variable individually or can you lock
them
all as a gr
The scope attribute was added in ColdFusion 4.5. In ColdFusion 4, you can
approximate this behavior by using the name attribute. For Session
variables, use the name #Session.SessionID#. For Application variables, use
the name #Application.ApplicationName#.
Benjamin S. Rogers
Web Developer, c4.net
In short
1) You need to have locks around even the Cfif Isdefined() statements. In
order for CF to check if a function is defined it has to attempt a read of
said function.
2) When accessing a shared variable to read its value the cflock type=""
attribute should be Readonly.
3) When acc
Jon Hall wrote:
> I have seen all of the warnings to make sure to use around any of
> the in memory variable types in a CF application. I hear that every access
> of a session, or application variable should have around it, or I
> could enable automatic locking on the server which will exact
6 matches
Mail list logo
