SNIP_ADAPTIVE_STD_FIGURE_Figure_6_17

Figure 6.17: BrakeEvent Class The using directive — analogue to the Proxy side — just introduces the common name SampleType for the concrete data type of the event. We provide two different variants of a ‘Send’ method, which is used to send out new event data. The first one takes a reference to a SampleType. This variant is straight forward: The event data has been allocated somewhere by the service application developer and is given via reference to the binding implementation of Send(). After the call to send returns, the data might be removed/altered on the caller side. The binding implementation will make a copy in the call. The second variant of ‘Send’ also has a parameter named ‘data’, but this is now of a different type ara::com::SampleAllocateePtr<SampleType>. According to our general approach to only provide abstract interfaces and eventually provide a proposed mapping to existing C++ types (see section 5.3) this pointer type, we introduced here, shall behave like a std::unique_ptr<T>. That roughly means: Only one party can hold the pointer - if the owner wants to give it away , he has to explic- 56 of 75 — AUTOSAR CONFIDENTIAL — Document ID 846: AUTOSAR_EXP_ARAComAPI