1 Preface
通常,阅读正式的规范并不是学习和理解某项技术的最简单的方法。对于AUTOSAR AP中的通信管理API (ara::com)来说尤其如此。因此,本文档不仅可作为Adaptive AP软件组件开发人员(他们将使用ara::com API与其他应用程序或服务组件进行交互)的切入点,也可作为Adaptive Platform产品供应商(他们将在其平台上实现ara::com API的optimizedIPCbinding)的切入点。 我们强烈建议读者在进入相关SWS的正式细节之前将此文档作为阅读的手头文件。
2. 后续主要章节的翻译笔记
第3章:
3.1 Approach
3.2 API Design Visions and Guidelines
第4章:
4.1 Proxy/Skeleton Architecture
4.2 Means of Communication
4.3 ara::com Event and Trigger based communication
4.4 ara::com Method based communication
4.5 ara::com Field based communication
4.6 Data Type Abstractions
4.7 Error Handling
4.8 Service Connection Approach(AutoSar AP 面向服务通信的提供者和消费者“连接”的方法)
4.8.1 Instance Identifiers and Instance Specifiers
4.8.2 When to use InstanceIdentifier versus InstanceSpecifier
第5章:
5.1 High Level API Structure
5.2 API Elements
5.3 Proxy Class
5.3.1 Proxy Class API’s
5.3.2 RadarService Proxy Class Example
5.3.3 Constructor and Handle Concept
5.3.4 Finding Services
5.3.4.1 Auto Update Proxy instance
5.3.5 Events
5.3.5.1 Event Subscription and Local Cache
5.3.5.2 Monitoring Event Subscription
5.3.5.3 Accessing Event Data — aka Samples
5.3.5.4 Event Sample Management via SamplePtrs
5.3.5.5 Event-Driven vs Polling-Based access
5.3.5.6 Buffering Strategies
5.3.6 Methods
5.3.6.1 One-Way aka Fire-and-Forget Methods
5.3.6.2 Event-Driven vs Polling access to method results
5.3.6.3 Canceling Method Result
5.3.7 Fields
5.3.8 触发器(Triggers)
5.4 骨架类(Skeleton Class)
5.4.1 Skeleton Class API
5.4.2 RadarService Skeleton Class 示例
5.4.3 实例化(构造函数)
AUTOSAR_EXP_ARAComAPI的5章笔记(10)
5.4.4. 提供服务实例
AUTOSAR_EXP_ARAComAPI的5章笔记(11)
5.4.5 轮询和事件驱动处理模式
5.4.5.1 轮询模式
5.4.5.2 事件驱动模式
AUTOSAR_EXP_ARAComAPI的5章笔记(12)
5.4.6 方法
5.4.6.1 单向(One - Way)又名即发即忘(Fire - and - Forget)方法
5.4.6.1 引发应用程序错误