> And if there is a need for cflock, why doesn't client vars > use them?
>There aren't any concurrency issues for Client variables. >They're not stored in memory. They're typically stored in a database It is my firm and biased opinion that memory variable concurrency locking should be part of the application server code and not performed in the scripting language or pseudo-code. However, I think I have said that before and am being repetitiously redundant. Best regards, Dennis Powers UXB Internet - A Web Design and Hosting Company tel: (203)879-2844 fax: (203)879-6254 http://www.uxbinternet.com/ http://dennis.uxb.net/ -----Original Message----- From: Dave Watts [mailto:[EMAIL PROTECTED]] Sent: Monday, April 22, 2002 11:23 AM To: CF-Talk Subject: RE: CF's Most Wanted :: > And if there is a need for cflock, why doesn't client vars > use them? There aren't any concurrency issues for Client variables. They're not stored in memory. They're typically stored in a database or registry, which will provide its own concurrency controls, or in cookies, which have no concurrency issues. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.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
