UDPSendReceiveServer

constructor(targetAddress: InetAddress, sendPort: Int, listenPort: Int, receiveBufferBytes: Int = MultiConnectionUDPServer.DEFAULT_RECEIVE_BUFFER_BYTES)(source)

Parameters

targetAddress

the address messages sent via send are delivered to

sendPort

the port on targetAddress that messages sent via send are delivered to

listenPort

the local port this server binds to receive incoming datagrams

receiveBufferBytes

size of the datagram receive buffer, 512..65507; defaults to 65507

No DeliveryMode / UdpChannel surface, by design

This type deliberately has no reliable-ordered channel, and never will. It is a standalone two-socket primitive (sendSocket plus a separately-bound listenSocket) with no handshake and no registration - there is no Connection here, and therefore no registered peer to key a ReliableChannelEngine or a retransmit schedule to. A reliable channel needs both; giving this type one would mean standing up a second, parallel reliability stack for a primitive nobody builds a session on. See docs/webtools-udp-architecture.md for the full reasoning.