Issues with binding and subscription handling

[DerAndereAndi]

Binding and subscription implementations or incomplete:

• Requesting (read) the list of bindings or subscriptions from a remote service doesn’t work. Incorrectly considered to be a “call” cmd. But not used so far by any device afaik
• Accepted outgoing binding and subscription requests are not stored locally, and therefor will not be provided in read requests
• Deleting bindings are only considered when coming in as a delete call from a remote client feature. But should also be possible from a remote server feature. But not used so far by any device afaik.
• Deleting bindings currently doesn’t allow to delete all bindings for an entity or a device for a client and server role-relation. But not used so far by any device afaik.
• If a remote declines a binding or subscription, this is currently not handled and also not exposed
• Last two points also apply to subscriptions

[DerAndereAndi]

Some analysis:

• The binding manager stores the data in a custom small data structure. If we store the data in bindingData, all updates from any device would be sent to any device.
• A reply currently creates the bindingData on the fly instead, so it can be filtered to the corresponding remote device.
• So the automatic notify does not work when updating the data. We can either shift to using the proper data set and then somehow integrate specific filters to run, or we extend the current mechanism for handling data updates and send relevant notifications.
• All the points also apply to the subscription manager and subscriptionData as well