iceoryx_posh 2.0.5
Loading...
Searching...
No Matches
Class Hierarchy

Go to the graphical class hierarchy

This inheritance list is sorted roughly, but not completely, alphabetically:
[detail level 123]
 Ciox::popo::BaseClient< PortT, TriggerHandleT >The BaseClient class contains the common implementation for the different clients
 Ciox::popo::BasePublisher< port_t >The BasePublisher class contains the common implementation for the different publisher specializations
 Ciox::popo::BaseServer< PortT, TriggerHandleT >The BaseServer class contains the common implementation for the different server
 Ciox::popo::BaseSubscriber< port_t >Base class for all types of subscriber
 Ciox::gw::Channel< IceoryxTerminal, ExternalTerminal >A data structure representing a channel between Iceoryx and an external system
 Ciox::mepoo::ChunkHeader
 Ciox::popo::ChunkSender< T >
 Ciox::mepoo::ChunkSettings
 Ciox::capro::ServiceDescription::ClassHash
 Ciox::popo::ClientOptionsThis struct is used to configure the client
 Ciox::config::CmdLineArgs_t
 Ciox::config::CmdLineParser
 CConfigParts
 Ciox::DefaultChunkDistributorConfig
 Ciox::DefaultChunkQueueConfig
 Ciox::roudi::DefaultRouDiMemory
 Ciox::mepoo::MePooConfig::Entry
 Ciox::popo::EventBasedTrigger_t
 Ciox::popo::EventCallback< OriginType, ContextDataType >
 Ciox::gw::GatewayBaseGeneric gateway for communication events
 Ciox::config::GatewayConfigGeneric configuration for gateways
 Ciox::gw::GatewayDiscovery< Impl_T >Discover the gateway
 Ciox::roudi::IceOryxRouDiComponents
 Ciox::popo::ListenerImpl< Capacity >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
 Ciox::popo::ListenerImpl< MAX_NUMBER_OF_EVENTS_PER_LISTENER >
 Ciox::roudi::MemoryBlockThe 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
 Ciox::mepoo::MemoryInfoStores properties of the memory to be used when we distinguish between different types of memory on e.g. different devices with different characteristics
 Ciox::roudi::MemoryProviderThis 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
 Ciox::roudi::MemPoolInfoStruct for the storage of mempool usage information. This data container is used by the introstpection::MemPoolInfoContainer array to store information on all available memmpools
 Ciox::roudi::MemPoolIntrospectionInfoTopic for the mempool introspection that a user can subscribe to
 Ciox::mepoo::MePooConfig
 Ciox::runtime::NodeClass which represents a node
 Ciox::popo::NotificationAttorneyClass which allows accessing private methods to friends of NotificationAttorney. Used for example by the WaitSet. Implements the Client-Attorney Pattern
 Ciox::popo::NotificationCallback< OriginType, ContextDataType >Struct describes a callback with a user defined type which can be attached to a WaitSet or a Listener
 Ciox::popo::NotificationInfoNotificationInfo holds the state of a trigger like the pointer to the triggerOrigin, the notification id and the callback
 Ciox::mepoo::NoUserHeaderHelper struct to use as default template parameter when no user-header is used
 Ciox::helper::Optimize< ConfigParts >
 Ciox::helper::Optimize< FinalArg >
 Ciox::helper::Optimize< FirstArg, RemainderArgs... >
 Ciox::runtime::PortConfigInfoStores 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)
 Ciox::roudi::PortDataContainer for common port data which is related to the subscriber port as well as the publisher port
 Ciox::roudi::PortIntrospectionFieldTopicTopic for the port introspection that a user can subscribe to
 Ciox::roudi::PortPool
 Ciox::roudi::PortThroughputData
 Ciox::roudi::PortThroughputIntrospectionFieldTopicTopic for the port throughput that a user can subscribe to
 Ciox::runtime::PoshRuntimeThe runtime that is needed for each application to communicate with the RouDi daemon
 CPoshRuntimeImpl
 Ciox::roudi::ProcessIntrospectionData
 Ciox::roudi::ProcessIntrospectionFieldTopicTopic for the process introspection that a user can subscribe to
 Ciox::popo::PublisherInterface< T, H >
 Ciox::popo::PublisherInterface< T, mepoo::NoUserHeader >
 Ciox::popo::PublisherOptionsThis struct is used to configure the publisher
 Ciox::roudi::RouDiAppBase class for RouDi daemons
 Ciox::config::RouDiConfig
 Ciox::roudi::RouDiConfigFileProviderBase class for a config file provider
 Ciox::roudi::RouDiMemoryInterface
 Ciox::roudi::RouDiMemoryManager
 Ciox::popo::RpcBaseHeader
 Ciox::popo::RpcInterface< RpcType, SendErrorEnum >
 Ciox::popo::RpcInterface< Request< Req >, ClientSendError >
 Ciox::popo::RpcInterface< Response< Res >, ServerSendError >
 Ciox::mepoo::SegmentConfig
 Ciox::mepoo::SegmentConfig::SegmentEntry
 Ciox::popo::ServerOptionsThis struct is used to configure the server
 Ciox::capro::ServiceDescriptionClass 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
 Ciox::runtime::ServiceDiscovery
 Ciox::config::GatewayConfig::ServiceEntry
 Ciox::helper::SetDefaults< ConfigParts >
 Ciox::helper::SetDefaults< FinalArg >
 Ciox::helper::SetDefaults< FirstArg, RemainderArgs... >
 CSmartChunk
 Ciox::popo::StateBasedTrigger_t
 Ciox::popo::SubscriberOptionsThis struct is used to configure the subscriber
 Ciox::roudi::SubscriberPortChangingData
 Ciox::roudi::SubscriberPortChangingIntrospectionFieldTopic
 Ciox::config::TomlGatewayConfigParserMethods for parsing gateway configs from toml text files
 Ciox::popo::TriggerUsually 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
 Ciox::popo::TriggerHandleTriggerHandle 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
 Ciox::popo::UserTriggerAn 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
 Ciox::popo::Void
 Ciox::popo::WaitSet< Capacity >Logical disjunction of a certain number of Triggers