Binary cap option

Binary cap option

Erlang runtime system for IP communication. Using the Kernel configuration parameters above, one can set default options for all TCP sockets on a binary cap option, but use this with care. Addresses as inputs to functions can be either a string or a tuple.

For example, the IP address 150. The record is defined in the Kernel include file “inet. This address family only works on Unix-like systems. It is limited in length by the operating system, traditionally to 108 bytes. Other addresses are possible, for example Linux implements “Abstract Addresses”. AF_UNSPEC and can occur if the other side has no socket address.

Closes a socket of any type. Found an issue with the documentation? Only actual parameters with other than default values are returned, for example not directives that specify other sources for configuration parameters nor directives that clear parameters. IP address, a single hostname, or a fully qualified hostname.

Returns a list of 2-tuples containing interface names and the interfaces’ addresses. OS call, on platforms that supports that feature. Gets one or more options for a socket. If the operating system fails to support an option, it is left out in the returned list. This behavior is kept for backward compatibility reasons.

The use of raw socket options makes the code non-portable, but allows the Erlang programmer to take advantage of unusual features present on a particular platform. In this case, the binary size is to correspond to the required buffer size of the return value. Asking for and inspecting raw socket options require low-level information about the current operating system and TCP stack. 28 bytes, and the value is a 32-bit integer. Preferably, you would check the machine type, the operating system, and the Kernel version before executing anything similar to this code. Gets one or more statistic options for a socket.