SocketOptions

This is an IPv4-only socket option whose functionality is subsumed by IP_MULTICAST_IF2 and not implemented on Android.

This integer option sets the outgoing interface for multicast packets using an interface index.

See RFC 1112: Host Extensions for IP Multicasting for more information about IP multicast.

This boolean option specifies whether the local loopback of multicast packets is enabled or disabled. This loopback is enabled by default on multicast sockets.

See RFC 1112: Host Extensions for IP Multicasting for more information about IP multicast.

See setLoopbackMode(boolean).

This integer option specifies the value for the type-of-service field of the IPv4 header, or the traffic class field of the IPv6 header. These correspond to the IP_TOS and IPV6_TCLASS socket options. These may be ignored by the underlying OS. Values must be between 0 and 255 inclusive.

See RFC 1349 for more about IPv4 and RFC 2460 for more about IPv6.

This option does not correspond to any Unix socket option and is not implemented on Android.

This boolean option can be used to enable or disable broadcasting on datagram sockets. This option must be enabled to send broadcast messages. The default value is false.

This boolean option specifies whether the kernel sends keepalive messages on connection-oriented sockets.

See RFC 1122: Requirements for Internet Hosts -- Communication Layers for more information on keep-alive.

Number of seconds to wait when closing a socket if there is still some buffered data to be sent.

The option can be set to disabled using setOption(int, Object) with a value of Boolean.FALSE.

If this option is set to 0, the TCP socket is closed forcefully and the call to close returns immediately. If this option is disabled, closing a socket will return immediately and the close will be handled in the background.

If this option is set to a value greater than 0, the value is interpreted as the number of seconds to wait. If all data could be sent during this time, the socket is closed normally. Otherwise the connection will be closed forcefully.

Valid numeric values for this option are in the range 0 to 65535 inclusive. (Larger timeouts will be treated as 65535s timeouts; roughly 18 hours.)

This option is intended for use with sockets in blocking mode. The behavior of this option for non-blocking sockets is undefined.

This boolean option specifies whether sending TCP urgent data is supported on this socket or not.

The size in bytes of a socket's receive buffer. This must be an integer greater than 0. This is a hint to the kernel; the kernel may use a larger buffer.

For datagram sockets, packets larger than this value will be discarded.

See RFC1323: TCP Extensions for High Performance for more information about TCP/IP buffering.

This boolean option specifies whether a reuse of a local address is allowed when another socket has not yet been removed by the operating system.

For connection-oriented sockets, if this option is disabled and if there is another socket in state TIME_WAIT on a given address then another socket binding to that address would fail. Setting this value after a socket is bound has no effect.

For datagram sockets this option determines whether several sockets can listen on the same address; when enabled each socket will receive a copy of the datagram.

See RFC 793: Transmission Control Protocol for more information about socket re-use.

The size in bytes of a socket's send buffer. This must be an integer greater than 0. This is a hint to the kernel; the kernel may use a larger buffer.

For datagram sockets, it is implementation-defined whether packets larger than this size can be sent.

Integer timeout in milliseconds for blocking accept or read/receive operations (but not write/send operations). A timeout of 0 means no timeout. Negative timeouts are not allowed.

An InterruptedIOException is thrown if this timeout expires.

This boolean option specifies whether data is sent immediately on this socket or buffered.

If set to Boolean.TRUE the Nagle algorithm is disabled and there is no buffering. This could lead to low packet efficiency. When set to Boolean.FALSE the the socket implementation uses buffering to try to reach a higher packet efficiency.

See RFC 1122: Requirements for Internet Hosts -- Communication Layers for more information about buffering and the Nagle algorithm.

Gets the value for the specified socket option.

Sets the value of the specified socket option.