Sorry, Matt, I didn't answer your question: > Now its my turn to say 'thats just plain wrong'. Or perhaps instead > "tell my why there is any reason whatsoever that code which creates a > benign race condition should be locked."
My reason is that, though the code is sacrificial, you should do your level best to ensure that when the code is executed it is accurate. Specifying a very short timeout ensures that performance won't be unduly affected, and so you get a true "sacrifice" of the code block in favor of performance because everything in the body of the CFLOCK is bypassed when a lock is not acquired while throwOnTimeout="No". Not locking that sacrificial code block allows the code to execute and possibly give incorrect results. Respectfully, Adam Phillip Churvis Member of Team Macromedia http://www.ProductivityEnhancement.com Download Plum and other cool development tools, and get advanced intensive Master-level training: * C# & ASP.NET for ColdFusion Developers * ColdFusion MX Master Class * Advanced Development with CFMX and SQL Server 2000 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:206025 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
