>the need for locks on the application-scope reads. (Feel free to
>refute that one, too. :)
Love to...
You don't need to lock variables in CFMX to keep from memory fragmentation
and server crashing. This is done for you by Java. You do need to lock if
there is potential for a race condition, where 2 people could write to the
same variable and cause general application havoc (for instance, 2 people
selecting the same unique record accidentally). If your application scoped
CFC reads and writes variables that can make changes to all users on your
site and can cause race conditions, you should lock, however, do the locking
IN the CFC, around the lines that require the locks, not outside and around
it.
-nathan strutz
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
