It's nice to hear someone else express this sentiment. (smile) Indeed, it doesn't make any sense. Multi-threaded applications are ubiquitous. Thousands of programmers have written code to properly manage access to shared memory resources. It's too bad none of them have worked for Allaire/Macromedia.
I suppose we should be generous and assume that some gnarly legacy issues caused Allaire to go with the CFLOCK kludge. But I understand that Neo is a complete rewrite of ColdFusion. If the locking issues are still present in Neo, it's going to seriously shake my faith in the quality of Macromedia software engineering. [EMAIL PROTECTED] ----- Original Message ----- From: "Howie Hamlin" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Monday, March 18, 2002 8:21 AM Subject: Re: UDF question > Why CF doesn't protect threaded access to shared memory automatically, I'll never know. It just doesn't make any sense. What if > you're a hosting provider? Do you have to check all of your clients' code for proper locks? As far as I know, CF is the only app > server that has this quirk and I think that locking memoy is something that should be handled behind the scenes. > > Maybe this limitation will be alleviated with NEO.... > > Howie ______________________________________________________________________ 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
