Content deleted Content added
Stevebroshar (talk | contribs) use Annotated link |
Stevebroshar (talk | contribs) name comes from AF_UNIX; Unix (not just any OS); singular over plural; if we're going to define an acronym might as well use it |
||
Line 1:
{{short description|
A '''Unix ___domain socket''' ('''UDS'''),
The name, ''Unix ___domain socket'', refers to the <code>___domain</code> argument value <code>AF_UNIX</code> that is passed to the function that creates a socket [[system resource]]. The communication ___domain is also selected by <code>AF_LOCAL</code>. <ref name="man-unix-sockets"></ref>
Valid
| url = http://man7.org/linux/man-pages/man7/unix.7.html
| date = 30 April 2018
Line 12 ⟶ 13:
* <code>SOCK_DGRAM</code> (compare to [[User Datagram Protocol|UDP]]) – for a datagram-oriented socket that preserves message boundaries (as on most UNIX implementations, UNIX ___domain datagram sockets are always reliable and don't reorder datagrams)
* <code>SOCK_SEQPACKET</code> (compare to [[SCTP]]) – for a sequenced-packet socket that is connection-oriented, preserves message boundaries, and delivers messages in the order that they were sent
The Unix ___domain socket facility is a standard component of [[POSIX]] [[operating system]]s.▼
▲The
The [[API]] for Unix ___domain sockets is similar to that of an [[Internet socket]], but rather than using an underlying network protocol, all communication occurs entirely within the operating system [[kernel (operating system)|kernel]]. Unix ___domain sockets may use the file system as their address [[name space]]. (Some operating systems, like [[Linux]], offer additional namespaces.) Processes reference Unix ___domain sockets as file system [[inode]]s, so two processes can communicate by opening the same socket.▼
▲The [[API]] for
In addition to sending data, processes may send [[file descriptor]]s across a
==See also==
|