I don't think anyone ever said that locking itself was broken. Locking scoped variable access should not have been required and that's what has been fixed (or improved... whatever).
As I speculated earlier, CFLOCK was a kludge to solve deficiencies in the original design of ColdFusion. Sometimes ugly things have to be done. That's OK. But declaring the kludge to be a wonderful feature was a silly thing to do. And carrying the kludge forward into the next generation product would have been, IMHO, pathetic. NEO=fixed is very good news! [EMAIL PROTECTED] ----- Original Message ----- From: "Lonny Eckert" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Thursday, March 21, 2002 9:10 AM Subject: RE: UDFs, CF Locking, etc., and NEO=fixed > > My personal speculation is that the current memory > > management code is probably the Three Mile Island part of > > the server codebase, and that even though its problems have > > been well understood for years, no one has been able to > > muster up the courage to try and work on it without having > > the entire server go up in a mushroom cloud. With Neo they > > could just abandon it rather than fix it, and so the > > problems are taken care of. > > First of all, I don't think anyone has made a compelling argument that > locking is broken. > > Secondly, commercial nuclear power reactors don't go up in mushroom clouds. > > > With Regards, > Lonny Eckert ex Health Physicist > BS RPI NE > MS GA Tech HP > > Lonny Eckert > Mi Services Group > [EMAIL PROTECTED] > (610) 230-2500 x147 > > ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.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
