The link was in response to the question of how future versions of CF would handle locking, and not part of a discussion on whether to cflock, I'll be sure to change my subject lines properly so that people don't get confused from now on. Since Java has no pointers, and everything (I could be wrong about that everything) is passed by reference, then it follows that the necessity of single threading code so that pointers do not get corrupted, or cause memory leaks, may not be necessary. Of course locking may still be required for counters and such...
jon ----- Original Message ----- From: "Howie Hamlin" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Monday, March 18, 2002 3:28 PM Subject: Re: UDF question > This article is about memory leaks caused by bad coding. We were talking about CFLOCKs and why the server should be doing > concurrency checking without the coder using CFLOCK at all. > > Howie > > ----- Original Message ----- > From: "Jon Hall" <[EMAIL PROTECTED]> > To: "CF-Talk" <[EMAIL PROTECTED]> > Sent: Monday, March 18, 2002 3:21 PM > Subject: Re: UDF question > > > > http://www.javaworld.com/javaworld/javaqa/1999-08/04-qa-leaks.html > > > > > > > ______________________________________________________________________ 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/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
