SNIP_ADAPTIVE_COM_FIGURE_Figure_6_6_ARACOMAPI

Figure 6.6: InstanceIdentifier Resolution Why this API does return a list of ara::com::InstanceIdentifier is in need of explanation: AUTOSAR supports, that the integrator may configure multiple technical bindings behind one abstract identifier visible to the software component developer. This feature is called multi-binding and referred to at different parts in this document (you find a more detailed explanation in section 7.3). Using multi-binding on the skeleton/server side is a common use case, since it simply allows different clients to use their preferred binding, when contacting the server. Contrary using multi-binding on the proxy/client side is a rather exotic one. E.g. it could be used to support some fail-over approaches (if binding A does not work, fall back on binding B). So the possible returns for a call of ResolveInstanceIdentifiers() are: • empty list: The integrator failed to provide a mapping for the abstract identifier. This most likely is a configuration error. 20 of 90 — AUTOSAR CONFIDENTIAL — Document ID 846: AUTOSAR_EXP_ARAComAPI