List,
I have yet another question about using CFLOCK to protect access to shared
variable scopes.
As I understand it, CFLOCKing reads and writes to the shared variable scopes
(session, application, server) prevents possible data corruption caused by
simultaneous reads and writes.
My question is: if the data in the shared scopes is written very
infrequently but read often, couldn't I just lock the writes and thereby
still avoid the possible corruption?
Here's the scenario: I keep structures and/or queries of often used
information in application scoped variables to avoid repetitive database
queries. This data rarely changes, so I'm wondering if I could bypass the
performance hit of CFLOCKING access to this data. As long as I lock any
updates to this data then there won't be any danger of corruption, correct?
Or am I way off base here?
Thanks in advance for any insight,
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.
