20182018 Ericsson AB. All Rights Reserved. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. socket socket.xml
socket Socket interface.

This module provides an API for the socket interface. It is used to create, delete and manipulate sockets.

 socket()

As returned by open/2,3,4 and accept/1,2.

 Accept a connection on a socket.

Accept a connection on a socket.

This call is used with connection-based socket types (stream or seqpacket). It extracs the first pending connection request for the listen socket and returns the (newly) connected socket.

 Bind a name to a socket.

Bind a name to a socket.

When a socket is created (with open), it has no address assigned to it. bind assigns the address specified by the Addr argument.

The rules used for name binding vary between domains.

 Close a socket.

Closes the socket.

Note that for e.g. protocol = tcp, most implementations doing a close does not guarantee that any data sent is delivered to the recipient before the close is detected at the remote side.

One way to handle this is to use the shutdown function (socket:shutdown(Socket, write)) to signal that no more data is to be sent and then wait for the read side of the socket to be closed.

 Initiate a connection on a socket.

This function connects the socket to the address specied by the SockAddr argument.

 Get an option on a socket.

Get an option on a socket.

What properties are valid depend both on Level and on what kind of socket it is (domain, type and protocol).

Not all options are valid on all platforms. That is, even if "we" support an option, that does not mean that the underlying OS does.

 Get an option on a socket.

Get an option on a socket.

What properties are valid depend both on Level and on what kind of socket it is (domain, type and protocol).

When specifying Level as an integer, and therefor using "native mode", it is *currently* up to the caller to know how to interpret the result.

Not all options are valid on all platforms. That is, even if "we" support an option, that does not mean that the underlying OS does.

 Listen for connections on a socket.

Listen for connections on a socket.

 Create an endpoint for communication.

Creates an endpoint (socket) for communication.

For some types there is a default protocol, which will be used if no protocol is specified:

stream: tcp

dgram: udp

seqpacket: sctp

The Extra argument is intended for "obscure" options. Currently the only supported option is netns, which is only supported on the linux platform.

 Get name of connected socket peer.

Returns the address of the peer connected to the socket.

 Receive a message from a socket.

Receive a message from a socket.

There is a special case for the argument Length. If it is set to zero (0), it means "give me everything you currently have".

 Receive a message from a socket.

Receive a message from a socket.

This function reads "messages", which means that regardless of how much we want to read, it returns when we get a message.

The BufSz argument basically defines the size of the receive buffer. By setting the value to zero (0), the configured size (setopt with Level = otp) is used.

It may be impossible to know what (buffer) size is appropriate "in advance", and in those cases it may be convenient to use the (recv) 'peek' flag. When this flag is provided, the message is *not* "consumed" from the underlying buffers, so another recvfrom call is needed, possibly with a then adjusted buffer size.

 Receive a message from a socket.

Receive a message from a socket.

This function reads "messages", which means that regardless of how much we want to read, it returns when we get a message.

The message will be delivered in the form of a msghdr(), which may contain the source address (if socket not connected), a list of cmsghdr_recv() (depends on what socket options have been set and what the protocol and platform supports) and also a set of flags, providing further info about the read.

The BufSz argument basically defines the size of the receive buffer. By setting the value to zero (0), the configured size (setopt with Level = otp) is used.

The CtrlSz argument basically defines the size of the receive buffer for the control messages. By setting the value to zero (0), the configured size (setopt with Level = otp) is used.

It may be impossible to know what (buffer) size is appropriate "in advance", and in those cases it may be convenient to use the (recv) 'peek' flag. When this flag is provided, the message is *not* "consumed" from the underlying buffers, so another recvmsg call is needed, possibly with a then adjusted buffer size.

 Send a message on a socket.

Send a message on a connected socket.

 Send a message on a socket.

Send a message on a socket. The destination, if needed (socket not connected) is provided in the MsgHdr, which also contains the message to send, The MsgHdr may also contain an list of optional cmsghdr_send() (depends on what the protocol and platform supports).

Unlike the send function, this one sends one message. This means that if, for whatever reason, its not possible to send the message in one go, the function will instead return with the remaining data ({ok, Remaining}). Thereby leaving it up to the caller to decide what to do (retry with the remaining data of give up).

Send a message on a socket.

Send a message on a socket, to the specified destination.

 Set options on a socket.

Set options on a socket.

What properties are valid depend both on Level and on what kind of socket it is (domain, type and protocol).

Not all options are valid on all platforms. That is, even if "we" support an option, that does not mean that the underlying OS does.

Sockets are set 'non-blocking' when created, so this option is *not* available (as it would adversely effect the Erlang VM to set a socket 'blocking').

 Set options on a socket.

Set options on a socket.

What properties are valid depend both on Level and on what kind of socket it is (domain, type and protocol).

Not all options are valid on all platforms. That is, even if "we" support an option, that does not mean that the underlying OS does.

Sockets are set 'non-blocking' when created, so this option is *not* available (as it would adversely effect the Erlang VM to set a socket 'blocking').

 Shut down part of a full-duplex connection.

Shut down all or part of a full-duplex connection.

 Get socket name.

Returns the current address to which the socket is bound.

 Report info about what the platform supports.

This function intends to retreive information about what the platform supports. Such as if SCTP is supported. Or which socket options are supported.

Examples

TBD