The caching of the strings for enums is the responsibility of the client.
Most clients fetch the type DBR_CONTROL_xxx at connection and then
only monitor the value/timestamp/status. This is true of CAU, DM, MEDM
at least. For a client to get the changes in the middle of operation
they would either have to
1)monitor the entire structure and then the network traffic is increased
significantly
2) do gets - then you have a polled system with increased struture size
We are now considering as one of the extensions to channel access in
version 4 - adding an event type that lets a regular monitor know that
the parameters that make up the largest composite type have changed -
then the client can reacquire the larger structure. Needless to say,
this is not yet done.
One way to prove that the string is working is to use the
dbpf - utility in the IOC.
Do you do this in an operational system - or as you are developing
an application?
Bob
- Navigate by Date:
- Prev:
Changing MBBO state strings & CA Clients Andrew Johnson
- Next:
Re: Changing MBBO state strings & CA Clients Jeff Hill
- Index:
1994
1995
1996
<1997>
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Changing MBBO state strings & CA Clients Jeff Hill
- Next:
Collaboration Meeting in May Bob Dalesio
- Index:
1994
1995
1996
<1997>
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|