Hi all,

I’m currently implementing the different subscription types in KNX4Go … and 
here I noticed something.
We create a SubscriptionRequestBuilder and here can add different types of 
fields and even combinations.
So we could create a subscription request with some on-value-change fields, 
some periodically pulled fields and some events/alarms.

Now does it actually make sense to have this sort of combinations? I mean the 
program processing the results has to be very flexible in this case.

Wouldn’t it make sense to have 3 different types of subscription requests?

Chris

Reply via email to