Locking variables is Scope specific. So yes, you do need to lock SESSION
variables in a different <cflock> than APPLICATION variables.
Sharon
At 04:59 PM 5/3/2000 -0500, Jennifer wrote:
>At 05:13 PM 5/3/00 -0400, you wrote:
>>The upgraded 4.5 server can enforce locking on application and session
>>variables. You just need to put a CFLOCK around your CFSET's.
>
>Silly. We already did that. You didn't read past the error message!
>
>Actually, the question was, has it always been a problem to lock
>Application variables and Session variables in the same lock? In the
>meantime, someone told me that 4.5, which is the version we're running in
>this case, has lock scopes, so the problem we encountered was expected.
>
>So the moral of the story is, lock your scopes separately, starting now.
>
>But thanks for trying!
>
>---------------------------------------------------------------------------
---
>Archives: http://www.eGroups.com/list/cf-talk
>To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=listsbody=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
>
------------------------------------------------------------------------------
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.
