I'd add a throwontimeout="yes" to your lock so you can catch and locks that timeout before locking.
For variables, you need to lock cfparam only if it's cfparam'ing session, application, or server scoped variables. I'd use a name lock around the cfdirectory, myself, just to coordinate accesses. Chris Norloff ---------- Original Message ---------------------------------- from: "FlashGuy" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] date: Wed, 09 Oct 2002 09:55:52 -0400 >I'm setting session variables and using <cflock > ><cflock type="exclusive" scope="session" timeout="5"> > <cfset SESSION.variable1 = "something1"> ></cflock> ><cflock type="exclusive" scope="session" timeout="5"> > <cfset SESSION.variable2 = "something2"> ></cflock> > >I'm also using <cfparam which is being picked up with a <cfdirectory. Do I have to >wrap the <cfparam with a <cflock also? > ><cfparam name="dir" default="d:\"> > > > >--------------------------------------------------- >Colonel Nathan R. Jessop >Commanding Officer >Marine Ground Forces >Guatanamo Bay, Cuba >--------------------------------------------------- > > > > ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
