Requirements

MessagePassing.ServerInterface

The message passing component shall provide a server interface that registers connection handlers and processes incoming requests.

MessagePassing.OSIndependentAPI

The message passing component shall provide an OS-independent API for OS-native IPC mechanisms.

MessagePassing.SafetyCertifiedTransportMechanism

The implementation under QNX shall use a safety-certified transport mechanism.

MessagePassing.PointToPointConnections

The message passing component shall support only point-to-point (1:1) connections between communication endpoints. N:M connections are explicitly excluded.

MessagePassing.SmallDataLowLatencyCommunication

The message passing component shall provide low-latency communication for small data between dedicated endpoints.

MessagePassing.SynchronousUnidirectionalCommunication

The communication shall support synchronous unidirectional message sending on a given connection. The send call blocks until the message has been transferred to the receiving side and a suitable handler has been identified.

MessagePassing.SynchronousBidirectionalCommunication

The communication shall support synchronous bidirectional request-response communication on a given connection. The send call blocks until a reply from the receiver has been received (SendWaitReply).

MessagePassing.AsynchronousUnidirectionalCommunication

The communication shall support asynchronous unidirectional message sending, where the send call returns after the local message passing layer has accepted the message. No guarantee is provided that the message is delivered to or processed by the receiver.

MessagePassing.SingletonFreeImplementation

The Message Passing library design shall not use any singletons.

MessagePassing.AllowsBoundedMonotonicMemoryAllocation

The Message Passing library design shall allow bounded monotonic memory allocation.

MessagePassing.AllowsResourceMockInjectionForTesting

The Message Passing library design shall allow resource mock injection for testing.