This clears it up a bit..
http://www.sys-con.com/coldfusion/archives/0208/Forta/index.html
-----Original Message-----
From: Andy [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 22, 2001 9:58 AM
To: CF-Talk
Subject: How to choose Name or Scope when locking
I haven't seen anything yet that talks explicitly about when to use the Name
attribute and when to use the Scope attribute. There have been a number of
threads around whether to single thread updates to a single table.
For example, lets say that I read from a table in two programs and
write/delete from a third. For this example, lets say I want to single
thread all writes. To do this, would you use scope="application"
type="readonly" to lock the two read queries and scope="application"
type="exclusive" around the write or would replace the scope attribute in
both with something like name="databasename.tablename"?
I'd appreciate a pointer to any articles out there that I can read on
creating an appropriate locking strategy? I am not looking for the basics
around locking before using session and application variables.
Thanks,
Andy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
