[APE Index] [APE Hierarchy] [Headers]
Unreliable Datagram Peer Associations. More...
#include <socket.h>
UDP duplex connections impliment a bi-directional point-to-point UDP session between two peer hosts. Two UDP sockets are typically used on alternating port addresses to assure that sender and receiver data does not collide or echo back. A UDP Duplex is commonly used for full duplex real-time streaming of UDP data between hosts.
[public]
Create a UDP duplex as a pair of UDP simplex objects bound to alternating and interconnected port addresses.
port | number to bind reciever. |
bind | address to bind this socket to. |
[public]
Disconnect and remove a UDP Duplex session.
[public]
Associate the duplex with a specified peer host. Both the sender and receiver will be interconnected with the remote host.
host | address to connect socket to. |
[public]
Associate transmitter and receiver with a subnet for multi-peer subnet media streaming.
subnet | address to operate under. |
[public]
Disassociate this duplex from any host connection. No data should be read or written until a connection is established.
[public]
Associate the duplex with itself only. This can be used as a "disconnect" on systems which do not define AF_UNSPEC. This also means any data sent by the socket will be received by itself.
[public]
Examine next waiting UDP packet in the buffer without actually removing it from the socket head.
length | of packet to accept. |
address | to store packet to examine. |
[public]
Read (receive) a UDP packet from the remote host using the simpex receiver.
maximum | length of packet to accept. |
address | to store packet received. |
[public]
Write (send) a UDP packet to the remote host using the simplex sender.
length | of packet to send. |
address | of packet to send. |
| Kdoc |