A handle to a datagram-oriented transport socket.

Socket is the base interface for reading and writing datagrams over some underlying transport. All reads and writes operate using Buf objects, which represent views into some memory region specific to the socket. This makes zero-copy reads and writes possible, if the implementation chooses to support it.

A future byte-oriented socket will be ByteSocket (which is reliable).

Unlike ReliableSocket, a Socket does not guarantee reliable or in-order delivery; datagrams may be dropped, duplicated, or reordered depending on the underlying transport. However, any ReliableSocket can be implicitly converted to and used as a Socket.

The underlying socket begins open, but may close at any time. Once closed, all operations on the socket will report failures. A Socket cannot be reopened. A new one must be provisioned from a Listener or a Connector.

A Socket is cheaply copyable and always safe to access, ensuring that the underlying socket state is valid as long as a handle is held. Users should drop their handles once no longer needed to ensure prompt resource reclamation.