In short, name locking provides more flexibility and granularity but also
requires better planning on lock usage. My personal best practice is to
always use scope locking for memory variables.
However that doesn't mean there is no place for name based locks. For
example, when I modify a file using cffile, I try to wrap the tag in a lock
like this...
<cflock name="#FullPath#/#FileName#" type="exclusive">
<cffile action="delete/write" file="#FullPath#/#FileName#" ...>
</cflock>
Then I use a readonly lock whenever I read from the file.
</rob>
-----Original Message-----
From: David Schmidt [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 14, 2002 10:42 AM
To: CF-Talk
Subject: using cflock with scope vs name
Is there a benefit to use the name= attribute rather than the scope=
attribute in a cflock statement. What is recommended?
Thanks,
Dave
______________________________________________________________________
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/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
