Unix Domain Sockets
Discussions advocating for Unix domain sockets over TCP localhost ports or pipes for efficient local inter-process communication, highlighting benefits like performance, portability, and simplicity without network stack overhead.
Activity Over Time
Top Contributors
Keywords
Sample Comments
What's wrong with forking and using a pipe or socket?
Hmmm wouldnt it have been better (for portability reasons) to implement the equivalent of unix domain sockets instead?
Hmmm wouldnt it have been better (for portability reasons) to implement the equivalent of unix domain sockets instead?
Unix domain stream sockets do not use tcp. Nor do unix datagram sockets use udp. They're much simpler.
It's unfortunate that Unix sockets isn't being used for local connections like this.
Unix domain sockets. Bidirectional, and you can use datagrams to bypass the effort of framing data yourself.
Using SOCK_SEQPACKET would be saner than pipes or SOCK_STREAM.
Why does everybody use tcp ports instead of file sockets for local communication?
Support for Unix sockets would be a gamechanger.
Any good examples of how the socket API could have been better if they did stick to the dominant abstraction?