Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "IPC"
m (→IPC Mechanisms) |
m (→References) |
||
| Line 16: | Line 16: | ||
== References == | == References == | ||
Some interesting reads on related subjects, available on the web: | Some interesting reads on related subjects, available on the web: | ||
| + | * [http://java.sun.com/javase/6/webnotes/trouble/TSG-VM/html/signals.html Integrating Signal and Exception Handling] | ||
* [http://www.ibm.com/developerworks/java/library/i-signalhandling/ Revelations on Java signal handling and termination] | * [http://www.ibm.com/developerworks/java/library/i-signalhandling/ Revelations on Java signal handling and termination] | ||
Revision as of 03:46, 15 July 2009
Introduction
Inter-Process Communication (IPC) for Java allows for an interaction between an application running in a Java virtual machine and its native environment. Although the term IPC is also known to denote communication across system boundaries, this particular implementation is limited to a well-known set of system-local mechanisms. Although the I/O primitives supported by the Java platform already allow for inter-process communication, their non-functional features related to performance or security, are inferior to some of the unsupported IPC mechanisms available on today's operating systems.
IPC Mechanisms
The following mechanisms are under consideration in the context of Java IPC:
- Signal
- Semaphore
- FIFO a.k.a. (Anonymous or Named) Pipe
- Shared Memory
- Domain Socket
As this is not about distributed systems, the following mechanisms are not under consideration:
- RPC (remoting)
- Socket (UDP or TCP)
Of course, these mechanisms are already supported by the Java platform.
References
Some interesting reads on related subjects, available on the web: