Last I heard - this is not an issue in either CF5 or CFMX. (I.e., you don't have to worry about leaving a lock unfinished.)
======================================================================= Raymond Camden, ColdFusion Jedi Master for Macromedia Email : [EMAIL PROTECTED] Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda > -----Original Message----- > From: Tim Painter [mailto:[EMAIL PROTECTED]] > Sent: Monday, July 08, 2002 2:47 PM > To: CF-Talk > Subject: Re: nuther lockin Q? > > > I thought that putting a cflocation inside a cflock was a bad > thing to do -- doesn't it lock up the server or something? > > In that case, I'd set a temp variable to the value of the > session variable inside the cflock and test that: > <cflock type="readonly" scope="session" timeout="10"> > <cfif not len(session.auth.iUserID)> > <cfset tempGO = true> > <cfelse> > <cfset tempGO = false> > </cflock> > > <cfif tempGo> > <cflocation url="../logout.cfm?reason=sessiontimeout" > addtoken="no"> > </cfif> > ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com 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
