> I really did search for this, but didn't find an answer. I'm > moving from CF 4 to 4.5, and have turned on "Automatic Read > Locking" in all scopes. Now I'm going through to see what's > broken as a result. Note that I'm trying to maintain > compatibility with 4.0 as much as possible. > > Is there any way to make CF understand that the first lock is > protecting that session scope? If you enable Automatic Read Locking in CF 4.5.x, it'll insist that any write to a memory variable be locked using a scoped lock. Your only solution, for compatibility across 4.0.x and 4.5.x, is to disable Automatic Read Locking. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
