> change anything... Also reads and writes to > application variables > should be locked so the outer CFIF is not > necessarily a good idea.
The outer CFIF is necessary so that once initialization is over, subsequent requests won't even try to obtain a lock. Otherwise, every request will try to obtain a lock. By the way, this is a familiar idiom in java called "double-checked locking". I'm glad it works in CF, because it may fail in java. See http://www.cs.umd.edu/~pugh/java/memoryModel/DoubleCheckedLocking.html ===== I-Lin Kuo Macromedia CF5 Advanced Developer Sun Certified Java 2 Programmer __________________________________ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Gold Sponsor - CFHosting.net http://www.cfhosting.net Message: http://www.houseoffusion.com/lists.cfm/link=i:4:189048 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
