A couple of general questions regarding locking session variables (CF
4.0.1):
Does a CFLOCK with name="#session.sesionid#" only lock the variables in
memory for that particular session, or does it lock all session
variables for the application?
The CF 4.0.1 documentation for CFLOCK has the following note:
-------------------------------------------------------------
Limit the scope of code that updates shared data. Exclusive locks are
required to ensure the integrity of these updates, but they have a
significant impact on performance. Read-only locks are faster. If you
have a performance-sensitive application, you should substitute
read-only locks for exclusive locks wherever it is possible, for
example, when updating shared data.
-------------------------------------------------------------
What's the point of using a read-only lock to improve performance of
updates if you chance the possibility of corrupting the data? Do you
gain anything in terms of data integrity over using no lock at all?
What's a reasonable value for the timeout attribute when working with
session variables? I can't think of a reason why 1 second shouldn't be
more than enough, but I don't see how setting it higher could hurt
either.
Jim
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
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.
