Hi all, Initially I introduced the „tag-query” for subscriptions as quite regularly there I didn#t want to list all tags, that I subscribe to, but wanted to be able to use queries to filter which ones I’m interested in.
However, when going through the current subscription/publication API, I think that might have been a bad idea. We could instead have queries be a special form of Tag … cause for example in ADS I could have a symbolic address and get a tag for that and read it. However, I currently would have to create a new Query in order to subscribe. This doesn’t sound good to me. So, what do you think? Should I refactor the SubscriptionAPI to use normal Tag instances … the protocol dependent address parsers could then continue to produce Tags or QueryTags … the main difference would be, that if I add a query tag to a read-request, building or executing that request should probably produce an error for that field. (Which matches what we discussed during the meetup … that drivers should use return codes more excessively to report if subscriptions are not supported for the current device) What do you folks think? Chris
