If that is the case Ray then it's a sad day for ColdFusion performance.
The only way around it that I can see if you have to lock the containing
structure is to have 2 locks to perform a write,
lock all alterations to server.cfa with a named lock on server.cfa. e.g.
name="server.cfa", so any structinserts or structdeletes to server.cfa are
locked.
Also read lock "server.cfa" whenever reading or writing to server.cfa.a, or
server.cfa.b
That way you can assure that you are never reading or writing to server.cfa
concurrently while also lock protecting the substructure in its own lock. It
should be far higher performance than locking out the server scope (though
you may end up with multiple nested locks to get at the data you want).
Cheers,
Aaron.
/****************************************
Aaron Shurmer
Senior Developer
Daemon Internet Consultants
ph +61 (0) 2 9380 4162
http://www.daemon.com.au/
engineered.innovation
****************************************/
-----Original Message-----
From: Raymond Camden [mailto:[EMAIL PROTECTED]]
Sent: Monday, 17 September 2001 10:29 PM
To: Spectra-Talk
Subject: RE: Large mod - locking explanation?
Geoff, yes, this is exactly the tone I took w/ our internal people. I
told them to assume that the code wrote perfect name locks.
FYI, as it stands, in my mind, if you work with server.cfa.a and
server.cfa.b, they are the same structure, just different parts of it,
and SCOPE locks are the correct way to do it.
Anyway, we are getting an official answer on this.
=======================================================================
Raymond Camden, Principal Spectra Compliance Engineer for Macromedia
Email : [EMAIL PROTECTED]
Yahoo IM : morpheus
"My ally is the Force, and a powerful ally it is." - Yoda
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Get the mailserver that powers this list at http://www.coolfusion.com
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
