ACE_RMCast | The RMCast namespace |
ACE_RMCast::Ack | Provide feedback to the sender about messages received and sent so far |
ACE_RMCast::Ack_Join | Receivers accept new members using this message |
ACE_RMCast::Ack_Leave | Senders acknowledge when receivers try to leave |
ACE_RMCast::Data | This is the main message sent by senders |
ACE_RMCast::Join | Receivers send this message to indicate they want to join |
ACE_RMCast::Leave | Receivers send this message to disconnect gracefully |
ACE_RMCast::Poll | |
ACE_RMCast_Ack_Worker | The retransmission module uses internal iterators, thus it needs to create helper Worker classes to process some messages |
ACE_RMCast_Copy_On_Write< KEY, ITEM, COLLECTION, ITERATOR > | Implement a copy on write wrapper for a map-like collection |
ACE_RMCast_Copy_On_Write_Collection< COLLECTION, ITERATOR > | A wrapper to implement reference counted collections |
ACE_RMCast_Copy_On_Write_Container< COLLECTION, ITERATOR > | Base class for the Copy_On_Write collection, used to simplify the declaration of the Write_Guard |
ACE_RMCast_Copy_On_Write_Read_Guard< COLLECTION, ITERATOR > | Implement a read guard for a reference counted collection |
ACE_RMCast_Copy_On_Write_Write_Guard< COLLECTION, ITERATOR > | Implement the write guard for a reference counted collecion |
ACE_RMCast_Fork | In some instances the messages must be sent to multiple destinations, this module is a generic component to duplicate such messages |
ACE_RMCast_Fragment | Fragmentation module |
ACE_RMCast_IO_UDP | |
ACE_RMCast_Membership | Reliable senders of events need to know exactly how many peers are receiving the events, and how many events has each peer received so far |
ACE_RMCast_Module | Reliable Multicast Module |
ACE_RMCast_Module_Factory | Create Module stacks |
ACE_RMCast_Partial_Message | Represent a partially received message in the ACE_RMCast_Reassembly module |
ACE_RMCast_Partial_Message::Hole | Represent a missing portion of a message |
ACE_RMCast_Proxy | Local representation for remote peers |
ACE_RMCast_Reassembly | Reassemble multiple data fragments into a single data message |
ACE_RMCast_Receiver_Module | A receiver proxy must reject invalid messages and communicate with the sender to join and leave the multicast group |
ACE_RMCast_Reliable_Factory | Many applications (and even some internal components), will use a single ACE_RMCast_Module to process all the events, for example, a receiver may decide to use the same ACE_RMCast_Module to process all incoming events, instead of using one per remote sender |
ACE_RMCast_Reordering | Some applications require receivers to process messages in the same order that messages are sent |
ACE_RMCast_Resend_Handler | Implement an adapter to resend messages in the ACE_RMCast_Retransmission layer, but based on Reactor based timeouts |
ACE_RMCast_Resend_Worker | The retransmission module uses internal iterators, thus it needs to create helper Worker classes to process some messages |
ACE_RMCast_Retransmission | Reliable configurations of the RMCast framework need to store messages on the sender side to resend them if one or more clients do not receive them successfully |
ACE_RMCast_Sequencer | On the sender side we must assign sequence numbers to the messages before they are put in the retransmission queue |
ACE_RMCast_Singleton_Factory | Many applications (and even some internal components), will use a single ACE_RMCast_Module to process all the events, for example, a receiver may decide to use the same ACE_RMCast_Module to process all incoming events, instead of using one per remote sender |
ACE_RMCast_UDP_Event_Handler | Implement an Adapter for the ACE_RMCast_IO_UDP class |
ACE_RMCast_UDP_Proxy | Proxy objects are transport specific, they are responsible for storing the remote peer addressing information |
ACE_RMCast_UDP_Reliable_Receiver | |
ACE_RMCast_UDP_Reliable_Sender | |
ACE_RMCast_Worker< KEY, ITEM > | |