Hi,
Everybody's favourite topic again.
I was checking some BOY screens and comparing the behaviour when switching from CA to PVA provider.
I noticed that with PVA provider the precision field is not obeyed whereas CA provider behaves like in the good old days.
Now, starting to track what is going on, I went to the Normative Types document and found the following sentence in the description of "display":
format
A format for converting the value field to a string Needs work: What is display.format? What's it for and what are examples? If it's a sprintf pattern, which syntax must it conform to - C or Java?
Looks like undone homework...
In addition, the scalar/scalarArray types have the metadata fields (alarm/time/display/control) as optional.
I do remember the discussions around this, even if only vaguely. I believe the intention here was to mimic CA behaviour where on defines the dbr type when calling ca operations (get/put/subscribe).
Two questions:
-does the PVA API still work like this? Does e.g., qsrv deliver the display field if a PVA clients asks for it?
-has the format field (as above) been defined in the mean time and I have missed the discussion? This looks rather unlikely but maybe.
I am sorry if this has already been discussed and clarified; in that case it just has not made its way to BOY/DiiRT or where it may be handled.
Or is this still an open issue? In that case I am afraid the Types and their behaviour/semantics has to be revisited. I know how much everybody loves these discussions...
Timo
|