TAO_AV  2.1.2
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Friends Macros Pages
Class Hierarchy

Go to the graphical class hierarchy

This inheritance list is sorted roughly, but not completely, alphabetically:
[detail level 123456]
oCACE_Connector_Base< class > [external]
|\CACE_Connector< TAO_AV_TCP_Flow_Handler, ACE_SOCK_CONNECTOR > [external]
| \CTAO_AV_TCP_Base_Connector
oCACE_Event_Handler [external]
|oCACE_Service_Object [external]
||oCACE_Acceptor< TAO_AV_TCP_Flow_Handler, ACE_SOCK_ACCEPTOR > [external]
|||\CTAO_AV_TCP_Base_Acceptor
||oCACE_Connector< TAO_AV_TCP_Flow_Handler, ACE_SOCK_CONNECTOR > [external]
||oCACE_Task_Base [external]
|||\CACE_Task< ACE_SYNCH_USE > [external]
||| \CACE_Svc_Handler< ACE_SOCK_STREAM, ACE_NULL_SYNCH > [external]
|||  \CTAO_AV_TCP_Flow_Handler
||oCTAO_AV_Flow_Protocol_Factory
|||oCTAO_AV_RTCP_Flow_Factory
|||oCTAO_AV_RTP_Flow_Factory
|||oCTAO_AV_SFP_Factory
|||oCTAO_AV_TCP_Flow_Factory
|||\CTAO_AV_UDP_Flow_Factory
||oCTAO_AV_Resource_FactoryTAO AV Streams default resource factory abstract The AV Streams resource factory loads the pluggable transport and flow protocol factories in the corresponding factory sets
|||\CTAO_AV_Default_Resource_FactoryTAO AV Streams default resource factory The AV Streams resource factory loads the pluggable transport and flow protocol factories in the corresponding factory sets
||\CTAO_AV_Transport_Factory
|| oCTAO_AV_TCP_Factory
|| \CTAO_AV_UDP_Factory
|oCTAO_AV_UDP_Flow_HandlerFlow Handler for UDP flows
|\CTAO_AV_UDP_MCast_Flow_HandlerFlow Handler for data sent over multicast sockets
oCACE_Shared_Object [external]
|\CACE_Service_Object [external]
oCAVStreams::alreadyConnected
oCAV_Null_MediaCtrl
oCAVStreams::Basic_StreamCtrlBase class for StreamCtrl, implements basic stream start and stop functionality
|\CAVStreams::StreamCtrlImplementation the A/V StreamCtrl class. this class is used to control the stream. It should be subclassed by applications that want to provide more control features
oCTAO_AV_RTP::bvchdr
oCTAO_AV_RTP::cellbhdr
oCflowProtocol::credit
oCAVStreams::deviceQosMismatch
oCAVStreams::failedToConnect
oCAVStreams::failedToListen
oCAVStreams::FDev
oCAVStreams::FEPMismatch
oCAVStreams::FlowConnection
oCAVStreams::FlowEndPoint
|oCAVStreams::FlowConsumer
|\CAVStreams::FlowProducer
oCAVStreams::flowStatusUsed to store the status of a flow
oCAVStreams::formatMismatch
oCAVStreams::formatNotSupported
oCAVStreams::FPError
oCflowProtocol::fragment
oCflowProtocol::frame
oCflowProtocol::frameHeader
oCAVStreams::InvalidPosition
oCAVStreams::invalidSettings
oCTAO_AV_RTP::jpeghdr
oCAVStreams::MCastConfigIfInterface for multicasting operations
oCMD5_CTX
oCTAO_AV_RTCP::md5_string
oCAVStreams::MediaControlMediaControl interface is similar to ControlledStream interface in MSS. It can be inherited by flow endpoints or FlowConnection interfaces
oCMediaTimer
oCAVStreams::MMDeviceImplements a factory to create Endpoints and VDevs
oCTAO_StreamCtrl::MMDevice_Map_Entry
oCMMDevice_Map_Hash_Key
oCAVStreams::NegotiatorThis interface is used to negotiate QoS between two stream endpoints
oCAVStreams::noSuchFlow
oCAVStreams::notConnected
oCAVStreams::notSupported
oCTAO_AV_RTCP::ntp64
oCNull_MediaCtrl
oCTAO_AV_RTP::nvhdr
oCTAO_MCastConfigIf::Peer_Info
oCAVStreams::Position
oCAVStreams::PostionKeyNotSupported
oCAVStreams::MediaControl::PostionKeyNotSupported
oCAVStreams::PropertyException
oCAVStreams::protocolNotSupported
oCAVStreams::QoSThis structure represents QoS for a given type. E.g. {"video_qos", <"video_framerate", 26>, <"video_depth", 9>}
oCAVStreams::QoSRequestFailed
oCRR_BlockThe receiver report block encapsulates the data that represents the reception statistics for a particular stream
oCRTCP_Channel_InSingle incoming data channel, or stream. The class has several responsibilities. When the class is instantiated, the incoming RTP traffic must be declared a valid source based on the RTP packets received. Once declared valie, this class is responsible for keeping up with reception statistics and other information. When an SR or RR is created (outside of this class), this class is used to get the Receiver Report block for this particular stream
oCRTCP_Channel_OutSingle outgoing data channel, or stream. It keeps track of statistics such as number of packets sent and number of bytes sent
oCRTCP_Common_HeaderThis is the header data that is common to all RTCP messages
oCRTCP_PacketThis is an abstract class from which all RTCP packet types are derived. It contains code used to validate the RTCP packet
|oCRTCP_BYE_PacketThe BYE RTCP packet is sent by a party when leaving an RTP session
|oCRTCP_RR_PacketThe Receiver Report packet is sent by all members of a session that are not sending data. It contains a list of RR_Block to represent each source this party is receiving data from
|oCRTCP_SDES_PacketThe Source Description packet is sent by all members of a session. At a minimum, the canonical name (or CNAME) is sent with each RTCP packet. Other items such as name, email, or location are included less frequently
|\CRTCP_SR_PacketThe Sender Report packet is sent by all members of a session that are sending data. It contains statistics on the data being sent out. It also contains a list of RR_Block to represent each source this party is receiving data from
oCTAO_AV_RTCP::rtcphdr
oCRTP_PacketThis class encapsulates all the necessary information to break down or build up an RTP data packet as well as operations to access all data items in the packet
oCTAO_AV_RTP::rtphdr
oCsdesChunk_sThis is a linked list of structures containing groups of source description items. A group of items for a particular synchronization source id is referred to as a 'chunk'
oCsdesItem_sThis is a linked list of structures containing source description 'items' such as canonical name, email, location etc
oCflowProtocol::sequencedFrame
oCAVStreams::SFPStatusThis structure is defined for SFP1.0 Subsequent versions of the protocol may specify new structures
oCflowProtocol::specialFrame
oCflowProtocol::Start
oCflowProtocol::StartReply
oCAVStreams::StreamEndPoint
|oCAVStreams::StreamEndPoint_AThe "A" side of a streamendpoint
|\CAVStreams::StreamEndPoint_BThe "B" side of a streamendpoint
oCStreamEndpointThe Stream EndPoint. Used to implement one endpoint of a stream that implements the transport layer
oCAVStreams::streamOpDenied
oCAVStreams::streamOpFailed
oCTAO_AV_Acceptor
|oCTAO_AV_TCP_Acceptor
|\CTAO_AV_UDP_Acceptor
oCTAO_AV_Acceptor_Registry
oCTAO_AV_Base_Connector
oCTAO_AV_CallbackCallback class that the user will be implementing for receiving frames from the network and also for timer events
|\CTAO_AV_RTCP_CallbackTAO_AV_Callback for RTCP protocol
oCTAO_AV_Child_Process< T_StreamEndpoint, T_VDev, T_MediaCtrl >Helper class for the child process created in TAO_AV_Endpoint_Process_Strategy
|oCTAO_AV_Child_Process_A< T_StreamEndpoint, T_VDev, T_MediaCtrl >Helper class for the child process created in TAO_AV_Child_Process
|\CTAO_AV_Child_Process_B< T_StreamEndpoint, T_VDev, T_MediaCtrl >Helper class for the child process created in TAO_AV_Child_Process
oCTAO_AV_Connector
|oCTAO_AV_TCP_Connector
|\CTAO_AV_UDP_Connector
oCTAO_AV_Connector_Registry
oCTAO_AV_CoreThis class encapsulates access to the TAO AV Core's resources and its state
oCTAO_AV_Endpoint_Strategy
|oCTAO_AV_Endpoint_Process_StrategyProcess-based strategy for creating endpoints. Abstract base class
||oCTAO_AV_Endpoint_Process_Strategy_AProcess-based strategy to create "A" type endpoints
||\CTAO_AV_Endpoint_Process_Strategy_BProcess-based strategy to create "B" type endpoints
|oCTAO_AV_Endpoint_Reactive_Strategy< T_StreamEndpoint, T_VDev, T_MediaCtrl >Reactive strategy base class
||\CTAO_AV_Endpoint_Reactive_Strategy_A< T_StreamEndpoint, T_VDev, T_MediaCtrl >Reactive strategy
|\CTAO_AV_Endpoint_Reactive_Strategy< T_StreamEndpoint, T_Vdev, T_MediaCtrl >
| \CTAO_AV_Endpoint_Reactive_Strategy_B< T_StreamEndpoint, T_Vdev, T_MediaCtrl >Reactive strategy
oCTAO_AV_Flow_Handler
|oCTAO_AV_TCP_Flow_Handler
|oCTAO_AV_UDP_Flow_HandlerFlow Handler for UDP flows
|\CTAO_AV_UDP_MCast_Flow_HandlerFlow Handler for data sent over multicast sockets
oCTAO_AV_Flow_Protocol_Item
oCTAO_AV_frame_info
oCTAO_AV_Policy
|oCTAO_AV_Payload_Type_Policy
|oCTAO_AV_RTCP_Sdes_Policy
|oCTAO_AV_SFP_Credit_Policy
|\CTAO_AV_SSRC_Policy
oCTAO_AV_Protocol_Object
|oCTAO_AV_RTCP_ObjectTAO_AV_Protocol_Object for RTCP protocol
|oCTAO_AV_RTP_ObjectTAO_AV_Protocol_object for the RTP protocol
|oCTAO_AV_TCP_ObjectTAO_AV_Protocol_Object for Transmission Control Protocol (TCP)
|oCTAO_AV_UDP_ObjectTAO_AV_Protocol_Object for the User Datagram Protocol (UDP)
|\CTAO_SFP_Object
| oCTAO_SFP_Consumer_Object
| \CTAO_SFP_Producer_Object
oCTAO_AV_QoSClass for getting and setting the QoS characteristics of an AV Stream
oCTAO_AV_RTCPEncapsulate the header format for the Real Time Control Protocol (RTCP)
oCTAO_AV_RTCP_Sdes
oCTAO_AV_RTPEncapsulate the Real Time Protocol (RTP) header format
oCTAO_AV_TransportA Base class for the different transport protocols. All the different transports should derive and implement the open,close,send and recv methods
|oCTAO_AV_TCP_TransportA transport abstraction for socket streams. Uses the ACE_SOCK_Stream to send the data
|oCTAO_AV_UDP_MCast_TransportA transport abstraction for Multicast dgram sockets. Uses the ACE_SOCK_Dgram_Mcast to send data
|\CTAO_AV_UDP_TransportA transport abstraction for udp sockets. Uses the ACE_SOCK_Dgram to send the data
oCTAO_AV_Transport_Item
oCTAO_AV_UDP_Connection_SetupThis class is a helper for the TAO_AV_UDP_Acceptor and TAO_AV_UDP_Connector. It basically just reduces duplicate code. It takes the address of the peer in the connection, whether or not it is a multicast connection, and whether it is a connector or acceptor; and creates the local address and flow handler associated with the connection
oCTAO_Base_StreamEndPoint
|oCTAO_FlowEndPointThis class is used per flow e.g video flow and an audio flow to encapsulate the transport details
||oCTAO_FlowConsumer
||\CTAO_FlowProducer
|\CTAO_StreamEndPointThe Stream EndPoint. Used to implement one endpoint of a stream that implements the transport layer
| oCTAO_StreamEndPoint_AThe "A" side of a streamendpoint
| \CTAO_StreamEndPoint_BThe "B" side of a streamendpoint
oCTAO_Basic_StreamCtrlBase class for StreamCtrl, implements basic stream start and stop functionality
|\CTAO_StreamCtrlImplementation the A/V StreamCtrl class. this class is used to control the stream. It should be subclassed by applications that want to provide more control features
oCTAO_FDev< T_Producer, T_Consumer >Implementation of the AV/Streams Flow Device. A FlowConnection is used to bind FDevs for flows, much like how a StreamCtrl is used to bind MMDevices for streams
oCTAO_FlowConnectionThis class currently supports only one producer and one consumer per flow
oCTAO_FlowSpec_EntryA helper entry class in the flow spec sequence passed to bind_devs
|oCTAO_Forward_FlowSpec_Entry
|\CTAO_Reverse_FlowSpec_Entry
oCTAO_MCastConfigIf
oCTAO_MediaControlAbstract Mediacontrol class. The following are to be handled by the specialized media control for the specific media like camera, speaker
oCTAO_MMDeviceImplements a factory to create Endpoints and VDevs
oCTAO_Negotiator
oCTAO_SFP_Base
oCTAO_SFP_Fragment_Node
oCTAO_SFP_Fragment_Table_Entry
oCTAO_SFP_Frame_State
oCTAO_Tokenizer
oCTAO_VDevImplements the VDev interface. One of these is created per connection, and represents device-specific parameters
\CAVStreams::VDevImplements the VDev interface. One of these is created per connection, and represents device-specific parameters