> > http://www.sys-con.com/coldfusion/archives/0208/Forta/
> >
> > I think Ben explains this pretty good here.
unfortunately, his article completely contradicts some of the statements
made earlier in this thread. Ben says:
"...CF developers typically create variables in the APPLICATION scope...and
are careful never to overwrite them. If an application contained variables
like this, variables that were never updated (after initial creation), you
wouldn't really need to lock them at all."
so according to Ben Forta, the only time you need to lock an application
variable is when you are changing the value (i.e. CFSET), *NOT* when you are
simply reading it (i.e. CFOUTPUT). But Zack said in a previous reply:
"IT IS AN ABSOLUTE NECESITY THAT YOU LOCK ALL SESSION, APPLICATION, AND
SERVER VARIABLES WHEN YOU WRITE OR READ THEM."
i will say that this is one thing that our organization is struggling
with... in almost every question, someone says one thing and someone else
says another. there doesn't seem to be much agreement anymore in the
community. perhaps this is because allaire has changed CF so much with 4 and
4.5, but it certainly doesn't look good when i research something like
CFLOCK and create a standard to use it only to find out that someone else is
saying otherwise.
anyone else feel like this?
-mike
------------------------------------------------------------------------------
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.
