Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "IPC"

m (Introduction)
m (Introduction)
Line 1: Line 1:
 
== Introduction ==
 
== 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.
 
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. Named Pipe
 +
* Shared Memory
 +
* Domain Socket

Revision as of 02:45, 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. Named Pipe
* Shared Memory
* Domain Socket

Back to the top