> I was told (always dangerous I suppose) that in CFMX shared > memory scope locking is no longer necessary. That does not > mean locking overall is not necessary, just shared memory > scope.
That's correct. You no longer have to use CFLOCK to prevent memory corruption when using shared memory variables in CF MX. That's described within the documentation, I'm sure. You may still need CFLOCK to prevent logical errors caused by race conditions, but in any case, if you forget, your server won't crash. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm 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
