> ... I've never really seen a guide to determining intelligent > cflock timeout values, so I just use something like 5 or 10 > seconds.
I don't think there is much useful general information for determining CFLOCK timeout values. The only general information I can come up with would go something like this: "Use values that work for you, but that won't cause unacceptable behavior in worst-case scenarios." The timeout value refers to how long the lock will wait to start, rather than how long the lock itself can be maintained, so if you specify a timeout value of "5", you're saying that the contents of the lock shouldn't be locked by another instance of the lock more than 5 seconds, or if those contents are locked for longer, then the current lock instance should give up waiting for the other instance to finish. On rereading that sentence, I realize it sounds confusing, but don't have a better explanation as an alternative. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Why Share? Dedicated Win 2000 Server � PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation � $99/Month � Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusionc 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
