The timeout is in seconds. How long it takes to obtain a lock, depends on the other locks in the application, the code in them, the number of usrs on your site, .... In short: it depends.
If throwontimeout = "no", CF will just continue executing after the </cflock> without generating an error. -----Original Message----- From: Kay Smoljak [mailto:[EMAIL PROTECTED]] Sent: maandag 17 december 2001 12:37 To: CF-Talk Subject: Just when you thought the topic of locking was completelyexhausted... I have a couple of questions about locking. Now, before you groan, I *do* know how I should be locking, where I should be locking, and why. What I am unclear on is exactly what the effects of using different values for timeout and throwontimout. I presume timeout is in seconds; how long should the average application require to obtain a lock? When should I set this value higher or lower? What is the prctical effect of having it too high or too low? Also, throwontimeout - if I set this to yes, I presume I should then be using cftry and cfcatch to handle the timeout? What if it's set to no? Will the request keep trying to obtain a lock? Any insight would be really great... I'm hoping to take the certification exam in January, and there's so many niggly areas where I just *have* to know :) Thanks, Kay. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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
