The two attributes are for two "types" of locks. (Darn, Dave Watts sure does this stuff better than I do.)
If you're locking access to SERVER, APPLICATION or SESSION scoped variables, then yes, you want to have a scope, not a name. ----- Original Message ----- From: "Yager, Brian T Contractor/NCCIM" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Tuesday, March 19, 2002 2:46 PM Subject: RE: Confessions of a sloppy non-CFLOCKer--Real question-- > So is it better to not have a name but have the scope? > > > > -----Original Message----- > From: Keith [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, March 19, 2002 2:43 PM > To: CF-Talk > Subject: Re: Confessions of a sloppy non-CFLOCKer--Real question-- > > > I believe if you give the lock a name, it overrides the scope. > > The name and scope attributes are mutually exclusive. > > ----- Original Message ----- > From: "Yager, Brian T Contractor/NCCIM" <[EMAIL PROTECTED]> > To: "CF-Talk" <[EMAIL PROTECTED]> > Sent: Tuesday, March 19, 2002 2:34 PM > Subject: RE: Confessions of a sloppy non-CFLOCKer--Real question-- > > > > Let me ask a question...When I right click on a cflock tag in CF studio 4.5, > I > > get the option to make it scope = "session". When I am finished, that > doesn;t > > make it in the code for some reason. When I add it manualy, I get an > error... > > > > > > Error Diagnostic Information > > Attribute set validation error in tag CFLOCK > > > > The tag has an invalid attribute combination: the most likely attribute > > combinations are > > > > Required attributes: 'SCOPE,TIMEOUT'. Optional attributes: > > 'THROWONTIMEOUT,TYPE'. > > Required attributes: 'TIMEOUT'. Optional attributes: > 'NAME,THROWONTIMEOUT,TYPE'. > > Other possible combination is > > (No suggestions) > > > > > > > > Do I need the scope? > > > > > > Brian Yager > > President - North AL Cold Fusion Users Group > > Sr. Systems Analyst > > NCCIM/CIC > > [EMAIL PROTECTED] > > (256) 842-8342 > > > > > > -----Original Message----- > > From: Keith [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, March 19, 2002 1:37 PM > > To: CF-Talk > > Subject: Confessions of a sloppy non-CFLOCKer > > > > > > <cfsetting EnableSillinessOnly="Yes"> > > <cfset vBadProgrammerType = "sloppy non-CFLOCKer"> > > > > <cftry> > > > > <cflock scope="session" timeout="150" throwontimeout="Yes" type="READONLY" > > > <cfset vMyName = session.UserName> > > </cflock> > > > > <cflock scope="server" timeout="150" throwontimeout="Yes" type="READONLY" > > > <cfset vMrWatts = server.MasterCFProgrammer> > > </cflock> > > > > <cfoutput> > > <cflock scope="application" timeout="150" throwontimeout="Yes" > type="READONLY" > > > > > I, #vMyName#, wish to apologize to #vMrWatts#. and to > > all #application.ListName# members. > > </cflock> > > > > <cflock scope="session" timeout="150" throwontimeout="Yes" type="READONLY"> > > I've been pushing a discussion of #session.DiscussionTopic# which, with my > own > > help, has gotten out of hand. If it's not already clear to everyone, I am a > > #vBadProgrammerType#. > > </cflock> > > > > <cflock scope="application" timeout="150" throwontimeout="Yes" > type="READONLY" > > > > > I, #vMyName# hereby repent. From this day forward, I will do my coding in > > the clean, profession style that has been recommended by prominent members > of > > #application.ListName#. > > </cflock> > > > > </cfoutput> > > > > <cfcatch type="Lock"> > > You all *are* enclosing your CFLOCKs in CFTRY/CATCH, aren't you? > > </cfcatch> > > </cftry> > > <cfsetting EnableSillinessOnly="No"> > > > > > > > > ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. 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
