On Wednesday, September 25, 2002, at 04:25 , Tilbrook, Peter wrote: > Under the CF5 Administrator it was possible to enforce locking of specific > variables (good for writing compliant code for a stable server). > > Is there the same option under CFMX (I cannae find it!).
CFMX does not require locking the way CF5 did. In CFMX, if you don't lock shared scope access / update, the server will not crash. All you have to worry about in CFMX is race conditions - where two threads of code might access / update the same variable at the same time and cause a conflict. To avoid that, use a named lock (not a scoped lock). I made some comments about this in my blog a while back: http://www.corfield.org/blog/2002_09_01_archive.html#81527680 Sean A Corfield -- http://www.corfield.org/blog/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ______________________________________________________________________ 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/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
