Dear Core-talkers,
There is a possible request from our operations group to show VAL fields of input records as having no write access, if the device support would overwrite any value written at the next record processing.
Technically, these fields are writable.
Functionally, there are issues:
- The writing client (even using put-callback) will get the new value and show the operation as having succeeded.
- Other clients doing gets or creating new subscriptions (e.g. newly opened panels) will see the new value.
- Existing subscriptions (e.g. archivers, gateways, already open panels) will not get an update and have no clue.
- Depending on the situation (DTYP, SCAN) this inconsistent state may last a while.
What are your thoughts on this?
Thanks,
~Ralph
