There's really not that much difference between the different communication channels. The differences are mostly in what can connect the communication channel. Internet sockets give the most flexibility and the least security without addition code. (At best, you can accept connections only from the local machine.) An anon pipe between parent and child provides the most security, but the least flexibility. (You'd have to your application a bit if you decided to move one of the processes to another machine.)
What are your needs? Is there a parent-child relationship between the two processes?
How does the output of process 1 get buffered?
Since you're asking what method to use to communicate, I presume you have control over he code of both apps. If so, you are free to disable buffering (or not) no matter what channel you use.
In reply to Re: One writer, one reader, FIFO? Unix domain socket?
by ikegami
in thread One writer, one reader, FIFO? Unix domain socket?
by creeble
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |