---- Original Message -----
From: "Dave Watts" <[EMAIL PROTECTED]>
> Just remember to lock all accesses to memory variables with CFLOCK.
I asked a similar kind of question earlier, but didn't get much of answer.
Are you saying I should lock all Session and Application variables?
Are the rest of my thoughts on this correct:
1. Lock the writing of variables as "Exclusive" and the reading of variables
as "ReadOnly"?
2. Enclose all references to SessionID and any other Session variables in a
CFLOCK (even when using sessionID in a URL?).
3. This is esentially the same for CF4 & CF4.5 aside from being able to
provide a lock scope instead of name in 4.5.
4. It is better to assign session variables to local varables in
Application.cfm so they only need to be CFLock-ed once there. Is it then
safe to use these local variables without using cflock on other pages & what
is the appropriate prefix for such local variables that are reinitalised on
every request?
Thanks for the help.
Ben.
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
