Re: EPICS Python client application survey

[Benjamin Franksen <benjamin.franksen@bessy.de>]

On Thursday 01 October 2009, Michael Abbott wrote:
> On Wed, 30 Sep 2009, Andrew Johnson wrote:
> >  * DBE_PROPERTY events.  Generated now on the VAL field of the mbb[io]
> > record types when someone changes one of the *ST fields, a DBE_PROPERTY
> > monitor allows a client to always know what the current ENUM strings
> > are.
>
> I guess that's easy enough: presumably if the DBE_PROPERTY bit is set in
> a CA request to a pre .14.11 server it'll have no effect, 

I'd think so.

> so I guess I
> can just add DBE_PROPERTY to my list of event types.

The idea is that you can set up two monitors: one with a simple DBR_ENUM (or 
DBR_ST_ENUM or DBR_TIME_ENUM) for frequent value and/or status changes 
(DBE_VALUE|DBE_STATUS); and another one with the full DBR_CTRL_ENUM for the 
(hopefully) very infrequent changes of the enumeration strings (requesting 
/only/ events of type only DBE_PROPERTY). Which means you save network 
bandwidth and IOC cpu load as compared to only one monitor requesting 
DBR_CTRL_ENUM for all event types.

Cheers
Ben