I guess I'm hoping that future versions of CF will require *less* locking. The whole locking thing is silliness that should be handled automatically within CF.
But the important point is that the "Single Threaded Sessions" option makes session variable locking unnecessary. And I'll bet a dollar that it doesn't have a discernable affect on real-world performance. Plus you get cleaner code. ----- Original Message ----- From: "Philip Arnold - ASP" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Thursday, November 22, 2001 12:19 PM Subject: RE: Complete lack of locking... > > No offense, but it sounds like urban legend to me. Assuming it's properly > > implemented, the "Single Threaded Sessions" option should only have a > > significant effect in situations where two ColdFusion requests > > are being made at the same time within the same session, i.e. when two > > browser framed windows are loaded at once. Even on a framed site, this > > would be a relatively rare event. > > > > I've never heard a convincing argument for locking session > > variable access. > > The only exception I make is when I don't have control of the CF > > Administrator settings. > > I make it a point to ensure Locking is in for all Server, Client and Session > variables - better safe than sorry > > You never know what they might do in future releases that may impact on your > code - why risk it > > It's like I never do <cfset "form.#FieldName#"=myValue> anymore - I always > use SetVariable > > Philip Arnold > Director > Certified ColdFusion Developer > ASP Multimedia Limited > T: +44 (0)20 8680 1133 > > "Websites for the real world" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
