Wikipedia is usually great for these purposes. RPC: Remote procedure call (RPC) is an Inter-process communication technology that allows a computer program to cause a subroutine or procedure to execute in another address space (commonly on another computer on a shared network) without the programmer explicitly coding the details for this remote interaction. IPC: Inter-process … Read more
IPC is inter-process communication. It describes the mechanisms used by different types of android components to communicate with one another. 1) Intents are messages which components can send and receive. It is a universal mechanism of passing data between processes. With help of the intents one can start services or activities, invoke broadcast receivers and … Read more
In terms of speed, the best cross-platform IPC mechanism will be pipes. That assumes, however, that you want cross-platform IPC on the same machine. If you want to be able to talk to processes on remote machines, you’ll want to look at using sockets instead. Luckily, if you’re talking about TCP at least, sockets and … Read more
Multiple options for IPC: Socket-Based (Bare-Bones) Networking not necessarily hard, but: might be verbose for not much, might offer more surface for bugs, as you write more code. you could rely on existing frameworks, like Netty RMI Technically, that’s also network communication, but that’s transparent for you. Fully-fledged Message Passing Architectures usually built on either … Read more
Personally I am quite fond of message queues and think they are arguably the most under-utilized IPC in the unix world. They are fast and easy to use. A couple of thoughts: Some of this is just fashion. Old things become new again. Add a shiny do-dad on message queues and they may be next … Read more
Unix IPC Here are the big seven: Pipe Useful only among processes related as parent/child. Call pipe(2) and fork(2). Unidirectional. FIFO, or named pipe Two unrelated processes can use FIFO unlike plain pipe. Call mkfifo(3). Unidirectional. Socket and Unix Domain Socket Bidirectional. Meant for network communication, but can be used locally too. Can be used … Read more
WCF is the best choice. It supports a number of different transport mechanisms (including Named Pipes) and can be completely configuration driven. I would highly recommend that you take a look at WCF. Here is a blog that does a WCF vs Remoting performance comparison. A quote from the blog: The WCF and .NET Remoting … Read more
If you create a PF_UNIX socket of type SOCK_STREAM, and accept connections on it, then each time you accept a connection, you get a new file descriptor (as the return value of the accept system call). This file descriptor reads data from and writes data to a file descriptor in the client process. Thus it … Read more
Anonymous pipes. Use Asynchronous operations with BeginRead/BeginWrite and AsyncCallback.
When selecting your IPC you should consider causes for performance differences including transfer buffer sizes, data transfer mechanisms, memory allocation schemes, locking mechanism implementations, and even code complexity. Of the available IPC mechanisms, the choice for performance often comes down to Unix domain sockets or named pipes (FIFOs). I read a paper on Performance Analysis … Read more