At 10:51 AM 11/28/00 , you wrote:
Dave, Patricia, Justin,
Thanks for all your suggestions..
in other languages, i've gotten into the habit of not leaving any locks
"open". that's why the concern about a cfabort before the /cflock. I
guess th elock would just timeout, but i'd prefer to know. In the interim,
instead of cfaborting within the lock, i can re-write to set a var if there
s/b a cfabort, and then do the abort after the end of the lock.
>When you do an isdefined, CF is attempting a read of the variable name.
>Yes. You do need a READ Lock around IsDefined Statements. I can't see why
>a CFABORT inside of the CFLOCK would cause any kind of problem. I know
>where your thought process is going... but I still sense no problem there.
>Perhaps someone else has a more definitive answer about that aspect of your
>question.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
