<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head><meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
<title>ccRTP: Underlying transport protocol socket classes.</title>
<link href="tabs.css" rel="stylesheet" type="text/css">
<link href="doxygen.css" rel="stylesheet" type="text/css">
</head><body>
<!-- Generated by Doxygen 1.5.9 -->
<div class="navigation" id="top">
<div class="tabs">
<ul>
<li><a href="index.html"><span>Main Page</span></a></li>
<li><a href="modules.html"><span>Modules</span></a></li>
<li><a href="annotated.html"><span>Classes</span></a></li>
<li><a href="files.html"><span>Files</span></a></li>
<li><a href="examples.html"><span>Examples</span></a></li>
</ul>
</div>
</div>
<div class="contents">
<h1>Underlying transport protocol socket classes.</h1><table border="0" cellpadding="0" cellspacing="0">
<tr><td></td></tr>
<tr><td colspan="2"><br><h2>Classes</h2></td></tr>
<tr><td class="memItemLeft" nowrap align="right" valign="top">class </td><td class="memItemRight" valign="bottom"><a class="el" href="class_r_t_p_base_u_d_p_i_pv4_socket.html">RTPBaseUDPIPv4Socket</a></td></tr>
<tr><td class="mdescLeft"> </td><td class="mdescRight">A UDP/IPv4 socket class targetted at RTP stacks. <a href="class_r_t_p_base_u_d_p_i_pv4_socket.html#_details">More...</a><br></td></tr>
<tr><td class="memItemLeft" nowrap align="right" valign="top">class </td><td class="memItemRight" valign="bottom"><a class="el" href="class_dual_r_t_p_channel.html">DualRTPChannel< BaseSocket ></a></td></tr>
<tr><td class="memItemLeft" nowrap align="right" valign="top">class </td><td class="memItemRight" valign="bottom"><a class="el" href="class_dual_u_d_p_i_pv4_socket.html">DualUDPIPv4Socket</a></td></tr>
<tr><td class="mdescLeft"> </td><td class="mdescRight">A socket class based on two UDP/IPv4 sockets. <a href="class_dual_u_d_p_i_pv4_socket.html#_details">More...</a><br></td></tr>
<tr><td colspan="2"><br><h2>Typedefs</h2></td></tr>
<tr><td class="memItemLeft" nowrap align="right" valign="top">typedef <a class="el" href="class_dual_r_t_p_channel.html">DualRTPChannel</a><br class="typebreak">
< <a class="el" href="class_r_t_p_base_u_d_p_i_pv4_socket.html">RTPBaseUDPIPv4Socket</a> > </td><td class="memItemRight" valign="bottom"><a class="el" href="group__sockets.html#gf75e80d04833a6b4f6337361357df7fe">DualRTPUDPIPv4Channel</a></td></tr>
<tr><td class="memItemLeft" nowrap align="right" valign="top">typedef <a class="el" href="class_r_t_p_base_u_d_p_i_pv4_socket.html">RTPBaseUDPIPv4Socket</a> </td><td class="memItemRight" valign="bottom"><a class="el" href="group__sockets.html#gd1b98c43bdf92c12e62abc6803cba1e7">SingleRTPChannel</a></td></tr>
<tr><td class="mdescLeft"> </td><td class="mdescRight">May be used in applications where using the same socket for both sending and receiving is not a limitation. <a href="#gd1b98c43bdf92c12e62abc6803cba1e7"></a><br></td></tr>
<tr><td class="memItemLeft" nowrap align="right" valign="top">typedef <a class="el" href="class_r_t_p_base_u_d_p_i_pv4_socket.html">SingleRTPChannel</a> </td><td class="memItemRight" valign="bottom"><a class="el" href="group__sockets.html#g17393838c3cd3a7f6af593338c18ace2">SymmetricRTPChannel</a></td></tr>
<tr><td class="mdescLeft"> </td><td class="mdescRight">Actually, RTP with a single channel can be called 'Symmetric RTP'. <a href="#g17393838c3cd3a7f6af593338c18ace2"></a><br></td></tr>
</table>
<hr><h2>Typedef Documentation</h2>
<a class="anchor" name="gf75e80d04833a6b4f6337361357df7fe"></a><!-- doxytag: member="channel.h::DualRTPUDPIPv4Channel" ref="gf75e80d04833a6b4f6337361357df7fe" args="" -->
<div class="memitem">
<div class="memproto">
<table class="memname">
<tr>
<td class="memname">typedef <a class="el" href="class_dual_r_t_p_channel.html">DualRTPChannel</a><<a class="el" href="class_r_t_p_base_u_d_p_i_pv4_socket.html">RTPBaseUDPIPv4Socket</a>> <a class="el" href="class_dual_r_t_p_channel.html">DualRTPUDPIPv4Channel</a> </td>
</tr>
</table>
</div>
<div class="memdoc">
<p>
</div>
</div><p>
<a class="anchor" name="gd1b98c43bdf92c12e62abc6803cba1e7"></a><!-- doxytag: member="channel.h::SingleRTPChannel" ref="gd1b98c43bdf92c12e62abc6803cba1e7" args="" -->
<div class="memitem">
<div class="memproto">
<table class="memname">
<tr>
<td class="memname">typedef <a class="el" href="class_r_t_p_base_u_d_p_i_pv4_socket.html">RTPBaseUDPIPv4Socket</a> <a class="el" href="class_r_t_p_base_u_d_p_i_pv4_socket.html">SingleRTPChannel</a> </td>
</tr>
</table>
</div>
<div class="memdoc">
<p>
May be used in applications where using the same socket for both sending and receiving is not a limitation.
<p>
</div>
</div><p>
<a class="anchor" name="g17393838c3cd3a7f6af593338c18ace2"></a><!-- doxytag: member="channel.h::SymmetricRTPChannel" ref="g17393838c3cd3a7f6af593338c18ace2" args="" -->
<div class="memitem">
<div class="memproto">
<table class="memname">
<tr>
<td class="memname">typedef <a class="el" href="class_r_t_p_base_u_d_p_i_pv4_socket.html">SingleRTPChannel</a> <a class="el" href="class_r_t_p_base_u_d_p_i_pv4_socket.html">SymmetricRTPChannel</a> </td>
</tr>
</table>
</div>
<div class="memdoc">
<p>
Actually, RTP with a single channel can be called 'Symmetric RTP'.
<p>
</div>
</div><p>
</div>
<hr size="1"><address style="text-align: right;"><small>Generated on Fri Jul 24 21:42:25 2009 for ccRTP by
<a href="http://www.doxygen.org/index.html">
<img src="doxygen.png" alt="doxygen" align="middle" border="0"></a> 1.5.9 </small></address>
</body>
</html>
