In Ben Forta's recent article on CFLOCK (http://www.allaire.com/handlers/index.cfm?ID=17196&Method=Full), he at one point says: "If you need to lock only part of the APPLICATION scope, consider using the NAME attribute instead of SCOPE. " I have a question about that. It's my understanding that application, session and server variables are internally handled by CF in the same manner as structures; in other words, there is a single structure called APPLICATION, and when I write <Cfset application.myvar = "blah"> I'm actually creating (or updating) a key called MYVAR with value "blah" in that structure. Is that correct? If so, then when I set or read ANY application variable, I'm really touching the underlying structure that contains them all. Wouldn't that "touch" need to be locked against any other touches to that structure? Isn't that line of reasoning the one that leads to the "don't use #application.applicationname# as a NAME attribute for a lock" idea? What am I missing here? Or is this just a simple difference of opinion between Ben and others? For those of us still on 4.01 and therefore unable to use SCOPE, it sure would be nice if everyone would agree on locking rules... ------------------------------- Martin Herbener [EMAIL PROTECTED] Kentucky Department of Education ------------------------------------------------------------------------------ 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.
