Another question on CFLOCK:
>From what I've read so far, the standard lock name relates to the scope
being accessed. For example, accesses to the application scope use a lock
name of #Application.ApplicationName# and accesses to the session scope use
a lock name that is unique to that user session, such as the concatenation
of the CFID and CFTOKEN.
If I have two different structures stored in the application scope, could I
use separate names when accessing each structure, thereby increasing
performance because users reading one struct aren't affected by users
accessing the other?
I store a great deal of information in the shared scopes. As a result,
almost every page in my application reads *something* from the shared scope.
If I use the application name as the lock name then two simultaneous users
doing totally different tasks could be affected by the other user's lock.
If I use names that relate to the task or data being read then it seems to
me that this wouldn't happen.
The only thing I can think of that would make this a bad idea is if the
entire scope needs to be locked, not just parts of it. Any ideas?
Regards,
Seth Petry-Johnson
Argo Enterprise and Associates
------------------------------------------------------------------------------
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.
