Jump to content

Inter-process communication

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Jsmethers (talk | contribs) at 00:24, 21 July 2006 (rv). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Inter-Process Communication (IPC) is a set of techniques for the exchange of data between two or more threads in one or more processes. Processes may be running on one computer or on two or more computers connected by a network. IPC techniques are divided into methods for message passing, synchronization, shared memory, and remote procedure calls (RPC). The method of IPC used may vary based on the bandwidth and latency of communication between the threads, and the type of data being communicated.

IPC may also be referred to as inter-thread communication and inter-application communication.

Implementations

There are a number of APIs which may be used for IPC. A number of platform independent APIs include the following:

The following are platform specific APIs:

Table of IPC Methods:

Method Provided by (Operating systems or other environments)
File All operating systems.
Signal Most operating systems; some systems, such as Windows, only implement signals in the C run-time library and do not actually provide support for their use as an IPC technique.
Socket Most operating systems.
Pipe All POSIX systems.
Named pipe All POSIX systems.
Semaphore All POSIX systems.
Shared memory All POSIX systems.
Message passing
(shared nothing)
Used in MPI paradigm, Java RMI, CORBA and others.
Memory map All POSIX systems; may carry race condition risk if a temporary file is used. Windows also supports this technique but the APIs used are platform specific.
Message queue Most operating systems.
Mailbox Some operating systems.

See also

References

  • Stevens, Richard. UNIX Network Programming, Volume 2, Second Edition: Interprocess Communications. Prentice Hall, 1999. ISBN 0130810819