Unix ___domain socket: Difference between revisions

Content deleted Content added
SpBot (talk | contribs)
PGibbons (talk | contribs)
Add note that ___domain sockets can be used as a capability system
Line 3:
Unix ___domain connections appear as [[byte stream]]s, much like network connections, but all data remains within the local computer. UNIX ___domain sockets use the file system as address name space, i.e. they are referenced by processes as [[inodes]] in the file system. This allows two distinct processes to open the same socket in order to communicate. However, the actual communication (the data exchange) does not use the file system, but buffers in kernel memory.
 
In addition to sending data, processes can send [[file descriptor]]s across a Unix ___domain socket connection (including file descriptors for ___domain sockets) using the sendmsg() and recvmsg() system calls. This means that ___domain sockets can be used as an [[object-capability model|object-capability]] communication system.
 
==External links==