| ▼Niox | |
| ►Ncapro | |
| ►CServiceDescription | Class for the identification of a communication event including information on the service, the service instance and the event id. A class object can be serialized/deserialized, so it is possible to send the information e.g. over a IPC channel |
| CClassHash | |
| ►Nconfig | |
| CCmdLineArgs_t | |
| CCmdLineParser | |
| CCmdLineParserConfigFileOption | |
| ►CGatewayConfig | Generic configuration for gateways |
| CServiceEntry | |
| CRouDiConfig | |
| CTomlGatewayConfigParser | Methods for parsing gateway configs from toml text files |
| CTomlRouDiConfigFileProvider | |
| ►Ngw | |
| CChannel | A data structure representing a channel between Iceoryx and an external system |
| CGatewayBase | Generic gateway for communication events |
| CGatewayDiscovery | Discover the gateway |
| CGatewayGeneric | A reference generic gateway implementation |
| ►Nhelper | |
| COptimize | |
| COptimize< FinalArg > | |
| COptimize< FirstArg, RemainderArgs... > | |
| CSetDefaults | |
| CSetDefaults< FinalArg > | |
| CSetDefaults< FirstArg, RemainderArgs... > | |
| ►Nmepoo | |
| CChunkHeader | |
| CChunkSettings | |
| CMemoryInfo | Stores properties of the memory to be used when we distinguish between different types of memory on e.g. different devices with different characteristics |
| ►CMePooConfig | |
| CEntry | |
| CNoUserHeader | Helper struct to use as default template parameter when no user-header is used |
| ►CSegmentConfig | |
| CSegmentEntry | |
| ►Npopo | |
| CBaseClient | The BaseClient class contains the common implementation for the different clients |
| CBasePublisher | The BasePublisher class contains the common implementation for the different publisher specializations |
| CBaseServer | The BaseServer class contains the common implementation for the different server |
| CBaseSubscriber | Base class for all types of subscriber |
| CChunkSender | |
| CClient | The Client class for the request-response messaging pattern in iceoryx |
| CClientImpl | The ClientImpl class implements the typed client API |
| CClientOptions | This struct is used to configure the client |
| CEventBasedTrigger_t | |
| CEventCallback | |
| CListener | |
| CListenerImpl | The Listener is a class which reacts to registered events by executing a corresponding callback concurrently. This is achieved via an encapsulated thread inside this class |
| CNotificationAttorney | Class which allows accessing private methods to friends of NotificationAttorney. Used for example by the WaitSet. Implements the Client-Attorney Pattern |
| CNotificationCallback | Struct describes a callback with a user defined type which can be attached to a WaitSet or a Listener |
| CNotificationInfo | NotificationInfo holds the state of a trigger like the pointer to the triggerOrigin, the notification id and the callback |
| CPublisher | The Publisher class for the publish-subscribe messaging pattern in iceoryx |
| CPublisherImpl | The PublisherImpl class implements the typed publisher API |
| CPublisherInterface | |
| CPublisherOptions | This struct is used to configure the publisher |
| CRequest | The Request class is a mutable abstraction over types which are written to loaned shared memory. These requests are sent to the server via the iceoryx system |
| CRequestHeader | |
| CResponse | The Response class is a mutable abstraction over types which are written to loaned shared memory. These responses are sent to the client via the iceoryx system |
| CResponseHeader | |
| CRpcBaseHeader | |
| CRpcInterface | |
| CSample | The Sample class is a mutable abstraction over types which are written to loaned shared memory. These samples are publishable to the iceoryx system |
| CServer | The Server class for the request-response messaging pattern in iceoryx |
| CServerImpl | The ServerImpl class implements the typed server API |
| CServerOptions | This struct is used to configure the server |
| CStateBasedTrigger_t | |
| CSubscriber | The Subscriber class for the publish-subscribe messaging pattern in iceoryx |
| CSubscriberImpl | The SubscriberImpl class implements the typed subscriber API |
| CSubscriberOptions | This struct is used to configure the subscriber |
| CTrigger | Usually managed by a factory class like a WaitSet and acquired by classes which would like to signal a notification. Multiple Trigger can share a common ConditionVariableData pointer so that multiple Trigger can signal a single instance |
| CTriggerHandle | TriggerHandle is threadsafe without restrictions in a single process. Not qualified for inter process usage. The TriggerHandle is generated by a Notifyable like the WaitSet and handed out to the user when they acquire a trigger. The TriggerHandle corresponds with an internal Trigger and is used to signal an event via the trigger method. When it goes out of scope it cleans up the corresponding trigger in the Notifyable |
| CUntypedClient | |
| CUntypedClientImpl | The UntypedClientImpl class implements the untyped client API |
| CUntypedPublisher | For the publish-subscribe messaging pattern in iceoryx |
| CUntypedPublisherImpl | The UntypedPublisherImpl class implements the untyped publisher API |
| CUntypedServer | |
| CUntypedServerImpl | The UntypedServerImpl class implements the untyped server API |
| CUntypedSubscriber | For the publish-subscribe messaging pattern in iceoryx |
| CUntypedSubscriberImpl | The UntypedSubscriberImpl class implements the untyped subscriber API |
| CUserTrigger | An event based trigger which can be used by the application developer directly. If you would like to trigger a WaitSet/Listener through an event of your class you should use the Trigger class |
| CVoid | |
| CWaitSet | Logical disjunction of a certain number of Triggers |
| ►Nroudi | |
| CDefaultRouDiMemory | |
| CGenericMemoryBlock | The GenericMemoryBlock is an implementation of a MemoryBlock for a common use case |
| CIceOryxRouDiApp | |
| CIceOryxRouDiComponents | |
| CIceOryxRouDiMemoryManager | |
| CMemoryBlock | The MemoryBlock is a container for general purpose memory. It is used to request some memory from a MemoryProvider, which can be POSIX SHM, the stack or something completely different. To be able to use the container, some functions need to be implemented. For most use cases the GenericMemoryBlock can be used, which is a templated class and implements the most common case |
| CMemoryProvider | This class creates memory which is requested by the MemoryBlocks. Once the memory is available, this is announced to the blocks, so that they can consume the memory for their needs. When the Memory is release, the blocks will also called to handle this appropriately, e.g. calling the destructor of the underlying type. This class is an interface with some default behavior and needs an implementation for real memory supply, e.g. a PosixShmMemoryProvider |
| CMemPoolInfo | Struct for the storage of mempool usage information. This data container is used by the introstpection::MemPoolInfoContainer array to store information on all available memmpools |
| CMemPoolIntrospectionInfo | Topic for the mempool introspection that a user can subscribe to |
| CPortData | Container for common port data which is related to the subscriber port as well as the publisher port |
| CPortIntrospectionFieldTopic | Topic for the port introspection that a user can subscribe to |
| CPortPool | |
| CPortThroughputData | |
| CPortThroughputIntrospectionFieldTopic | Topic for the port throughput that a user can subscribe to |
| CPosixShmMemoryProvider | Creates the shared memory based on a provided configuration |
| CProcessIntrospectionData | |
| CProcessIntrospectionFieldTopic | Topic for the process introspection that a user can subscribe to |
| CPublisherPortData | Container for publisher port introspection data |
| CRouDiApp | Base class for RouDi daemons |
| CRouDiConfigFileProvider | Base class for a config file provider |
| CRouDiMemoryInterface | |
| CRouDiMemoryManager | |
| CSubscriberPortChangingData | |
| CSubscriberPortChangingIntrospectionFieldTopic | |
| ►Nruntime | |
| CNode | Class which represents a node |
| CPortConfigInfo | Stores information necessary to create the right type of port on RouDi side. Different types of ports are required if e.g. different types of shared memory are used (e.g. on GPU) |
| CPoshRuntime | The runtime that is needed for each application to communicate with the RouDi daemon |
| CPoshRuntimeSingleProcess | |
| CServiceDiscovery | |
| CConfig | |
| CDefaultChunkDistributorConfig | |
| CDefaultChunkQueueConfig | |
