Menu
Whats the different between IPC and Unix domain sockets and named pipes?
I got vague definitions from various books but couldn't get clarity on which one should be used where.
472
The named pipe transmitted at a speed of 318 Mbits/s, while the UNIX socket transmitted at 245 Mbits/s. So, in relative terms, named pipes are approximately 30% faster than UNIX sockets with a block size of 100 bytes.
A socket pair is much like a pipe; the main difference is that the socket pair is bidirectional, whereas the pipe has one input-only end and one output-only end (see Pipes and FIFOs).
What is the difference between socket and pipe? A socket is a part of the OSI model that enables communication between different layers. Pipes are used in processing in the CPU. Communication in socket is bi directional while it's unidirectional in pipes.
IPC based communication between local processes on an Android based mobile device (implementation platform for the prototype MCxB) is an order of magnitude faster and less resource intensive than HTTP based communication between the processes ( Kiani et al., 2011 ).
Just about any way two processes communicate with each other could be considered a form of IPC.
For example:
55
As qrdl stated, UNIX-domain sockets and named pipes are both IPC mechanisms.
Of these two, named pipes are simpler to work with, but much less flexible than UNIX-domain sockets. For example, if you potentially expect more than one reading process for each writing process, then UNIX-domain sockets are a must; if you expect the reading process to stop and start during the execution of the writing process, then you'll need UNIX-domain sockets.
21
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
