You don't "have" to lock down absolutely every reference to the shared
scopes anymore, but it is still a good idear. There is no longer the threat
of server corruption, but your variable's values can still be corrupted. So,
use cflock for {buzzword warning} race-time conditions like Raymond pointed
out and other variable's values you want to ensure are correct (like a
session shopping cart structure). You don't have to if you don't want to,
you just chance the wrong values being set.
Tyler Silcox
email | [EMAIL PROTECTED]
----- Original Message -----
From: "Gyrus" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Wednesday, May 01, 2002 4:48 PM
Subject: Re: CF Wishlist
> From: "Raymond Camden" <[EMAIL PROTECTED]>
>
> cflock is _not_ necessary for memory issues anymore. You still need it
> for logical reasons. For example:
>
> application.x = application.x + 1
Whoah - not been following this thread closely, but did I miss
something? You don't need to habitually lock Session, Server and
Application variables anymore in CFMX?
- Gyrus
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- [EMAIL PROTECTED]
work: http://www.tengai.co.uk
play: http://www.norlonto.net
- PGP key available
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
______________________________________________________________________
Get the mailserver that powers this list at http://www.coolfusion.com
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
