MICROSAR QuickCom generates a C++ Proxy/Skeleton API from your communication model definition. With this API you can define the proxy and skeleton implementation for your services.

Simplified proxy/skeleton architecture
Simplified proxy/skeleton architecture

Generation from the Service Interface Definition

The service interface definitions of the applications lay the groundwork for the Proxy/Skeleton API. The service interfaces are defined in the JSON configuration file of the application. The ProvidedPorts or RequiredPorts of the executables of the application reference the service interfaces. With this information MICROSAR QuickCom ModelBuilder generates the proxy and skeleton classes.

What is a service proxy?

In MICROSAR QuickCom a proxy is a generated class that applications can use to consume services.

Relevant setting in the JSON configuration: RequiredPorts

See Instantiate Service Proxy

What is a service skeleton?

In MICROSAR QuickCom a skeleton is a generated abstract class that applications can use to offer services.

Relevant setting in the JSON configuration: ProvidedPorts

See Implement Service Skeleton