API namespaces - api names should not be hardcoded in the JSON definition
Description
API namespace. API names are hardcoded in the JSON description at the moment and there is no way to have multiple instances of the same binding. This is a limitation being run into in the audio area and vehicle signaling where there can be multiple physical devices that need to be supported via the same API.
The actually availables "dynapi" used by audio and controler will be reworked to become the apiv3 that will allow that features.
I will present it at Karslruhe (spring 2018)
Jose Bollo
November 2, 2017 at 2:34 PM
(edited)
There is already work in progress. There is something in the discussion that must be detailed: what does mean "there is no way to have multiple instances of the same binding"? Does it mean:
that a same library should be able to provide several API names?
that a same API name can be implenmented using several bindings? I can not supply the latter be the former already has some draft implementation.
API namespace. API names are hardcoded in the JSON description at the moment and there is no way to have multiple instances of the same binding. This is a limitation being run into in the audio area and vehicle signaling where there can be multiple physical devices that need to be supported via the same API.