At 10:15 AM 5/24/00 -0400, Dave Watts wrote: >It's been brought to my attention that Allaire has posted a guide to using >CFLOCK in CF 4.5: > >http://www.allaire.com/Handlers/index.cfm?ID=14165&Method=Full That didn't quite answer all my questions, so I asked the "one guy on Earth who should know", Simeon Simeonov. (Dave, thanks for the pointer.) He says: * "In 4.5 you should lock around every access (read, write, lookup) to shared data. If you do this you will be 100% protected." * You do NOT need put CFLOCK around CFLOCATION. * You DO need to lock IsDefined(), "since you are looking at shared values." * You do not need to lock CFHTTP, CFFTP, etc. "If they don't use shared data, don't lock them." I (Greg) have seen some people complain about a limit on the number of CFHTTP requests that CF could handle, and when I mentioned this to Simeon, and he responded "This seems to have been a suggestion to work around a bug in the product. The CFHTTP code in 4.5 is new and should not cause any problems. One caveat, though. I'm not fully synched with the tech support & bug queues." * "We recommend that you always use lock detection during development and that, as much as you can, you stick to scope= type locks. In 4.5 they also run faster than dynamic name locks." One other item: it appears that the "throwOnTimeout" parameter of CFLOCK has no effect. I have posted this as a bug to http://forums1.allaire.com/devconf/Thread.cfm?&Thread_ID=164668&mc=1; if anyone knows a more direct way to submit a bug report, please let me know. Gregory M. Saunders, Ph.D. Senior Design Architect Cognitive Arts Corporation (http://www.cognitivearts.com) 120 S. Riverside Plaza, Suite 1520 Chicago, IL 60606 ------------------------------------------------------------------------------ Archives: http://www.eGroups.com/list/cf-talk To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
