iqueue(3) [debian man page]

Generic RTP input queues.(3)				     Library Functions Manual				      Generic RTP input queues.(3)

NAME

       Generic RTP input queues. -

   Classes
       class Members
	   members and senders accounting
       class SyncSourceHandler
	   SyncSource objects modification methods.
       class ParticipantHandler
	   Participant objects modification methods.
       class ApplicationHandler
	   Application objects modification methods.
       class ConflictHandler
	   To track addresses of sources conflicting with the local one.
       class MembershipBookkeeping
	   Controls the group membership in the current session.
       class IncomingDataQueue
	   Queue for incoming RTP data packets in an RTP session.

Detailed Description
Author
       Generated automatically by Doxygen for ccRTP from the source code.

ccRTP								  Sat Jun 23 2012				      Generic RTP input queues.(3)

Participants and synchronization sources.(3)		     Library Functions Manual		      Participants and synchronization sources.(3)

NAME

       Participants and synchronization sources. -

   Classes
       class SDESItemsHolder
	   Holds the SDES items and related information from a participant in an RTP application.
       class Participant
	   A class of objects representing remote participants (RTP applications) in a multimedia session.
       class SyncSource
	   Synchronization source in an RTP session.
       class RTPApplication
	   An RTP application, holding identifying RTCP SDES item values.

   Functions
       __EXPORT RTPApplication & defaultApplication ()
	   Get the RTPApplication object for the 'default' application (the only one used by common applications -those that only implement one
	   'RTP application').

Detailed Description
Function Documentation
   __EXPORT RTPApplication& defaultApplication ()
       Get the RTPApplication object for the 'default' application (the only one used by common applications -those that only implement one 'RTP
       application'). Note that this application object differs from all the others that may be defined in that it is automatically constructed by
       the ccRTP stack and its CNAME is automatically assigned (as user@host), whereas the other application objects' CNAME is provided to its
       constructor.

       Examples:
	   ccrtptest.cpp, rtphello.cpp, rtplisten.cpp, and rtpsend.cpp.

Author
       Generated automatically by Doxygen for ccRTP from the source code.

ccRTP								  Sat Jun 23 2012		      Participants and synchronization sources.(3)