PCAS service snap-in has no way to determine if its a put, or a put calback
Bug #541384 reported by
Jeff Hill
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
EPICS Base |
Fix Released
|
Wishlist
|
Jeff Hill |
Bug Description
In the CA communication model a put callback request causes a very different interaction model in the IOC core database compared to an ordinary unacknowledged put. The PCAS service should have some way to determine if the write request was intiated by a ca_put or a ca_put_callback.
Original Mantis Bug: mantis-358
http://
To post a comment you must log in.
It seems that we will need to add an attribute to the GDD that is being passed in.