no_delay() [2/2]

socket & xtd::net::sockets::socket::no_delay

(

bool

value

)

Gets a boolean value that specifies whether the stream xtd::net::sockets::socket is using the Nagle algorithm.

Parameters

value

false if the xtd::net::sockets::socket uses the Nagle algorithm; otherwise, true. The default is false.

Returns

This current instance.

Exceptions

xtd::net::sockets::socket_exception	This option is valid for a datagram socket only.
xtd::object_closed_exception	The xtd::net::sockets::socket has been closed.

Remarks

The Nagle algorithm is designed to reduce network traffic by causing the socket to buffer small packets and then combine and send them in one packet under certain circumstances. A TCP packet consists of 40 bytes of header plus the data being sent. When small packets of data are sent with TCP, the overhead resulting from the TCP header can become a significant part of the network traffic. On heavily loaded networks, the congestion resulting from this overhead can result in lost datagrams and retransmissions, as well as excessive propagation time caused by congestion. The Nagle algorithm inhibits the sending of new TCP segments when new outgoing data arrives from the user if any previously transmitted data on the connection remains unacknowledged.

The majority of network applications should use the Nagle algorithm.

Setting this property on a User Datagram Protocol (UDP) socket will have no effect.

Note

If you receive a xtd::net::sockets::socket_exception exception, use the xtd::net::sockets::socket_exception::error_code property to obtain the specific error code. After you have obtained this code, refer to the Windows Sockets version 2 API error code documentation in the MSDN library for a detailed description of the error.