Experimental Physics and
Industrial Control System

Tim Mooney <[email protected]> · Thu, 17 Apr 2003 23:05:16 -0500

Benjamin Franksen wrote:

> PS: I finally understood the S_db_Blocked issue (after reading the code
> in base and then re-reading the doc): S_db_Blocked is only returned if
> an existing put notify block in the target record is the *same* object
> (address comparison) as the one that is now being given as argument.
> Multiple putNotifies to the same target record seem to be no problem at
> all as long as they come from different clients, otherwise they are
> ignored. This is make sense, indeed. The Developer's Guide could be a
> little more clear on this point; it says "If a putNotify is already
> active..." which is of course fine if one already knows what is meant.

Uh-oh.  This isn't the way I understood putNotify.  It would be a disaster
for one client to initiate a putNotify trace on the same record, or even a
different record in the same lockset, as an ongoing putNotify trace.  How
could you ensure that the two execution traces would not interfere with
each other?

-- 
Tim Mooney ([email protected]; 630-252-5417)
Advanced Photon Source
APS Operations Division
Beamline Controls & Data Acquisition Group

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System