Groups > comp.lang.java.programmer > #11732

Re: Interplatform (interprocess, interlanguage) communication

Path	csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!newsfeed.freenet.ag!feeder2.ecngs.de!ecngs!feeder.ecngs.de!Xl.tags.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!local2.nntp.ams.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date	Sat, 04 Feb 2012 02:24:34 -0600
From	Leif Roar Moldskred <leifm@dimnakorr.com>
Subject	Re: Interplatform (interprocess, interlanguage) communication
Newsgroups	comp.lang.java.programmer
References	<IPC-20120203200443@ram.dialup.fu-berlin.de>
User-Agent	tin/2.0.0-20110823 ("Ardenistiel") (UNIX) (Linux/3.0.0-15-generic-pae (i686))
MIME-Version	1.0
Content-Type	text/plain; charset=UTF-8
Content-Transfer-Encoding	8bit
Message-ID	<IfKdneE9tPjfdrHSnZ2dnUVZ7sOdnZ2d@giganews.com> (permalink)
Date	Sat, 04 Feb 2012 02:24:34 -0600
Lines	40
X-Usenet-Provider	http://www.giganews.com
X-Trace	sv3-MyKbFx6IzmpFXnfMr2fPt4E5Hs13tAo9BAEC+2TBVKIdEryeXusVYX0fZJ0u8L2L2x62YFzmYDk84WF!VtiSMHlYruHlPoAQmLzvtEaAdcWH0RoVpI3CvnCv/rYHLFbYahJvFSMbFgtVsGjvh2mdiQ7/IqM=
X-Complaints-To	abuse@giganews.com
X-DMCA-Notifications	http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info	Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info	Otherwise we will be unable to process your complaint properly
X-Postfilter	1.3.40
X-Original-Bytes	2755
Xref	x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:11732

Show key headers only | View raw

Stefan Ram <ram@zedat.fu-berlin.de> wrote:

>  My criteria are: reliability and it should not be extremely
>  slow (say exchanging a string should not take more than
>  about 10 ms). The main criterion is reliability.
> 
>  »Reliability« means little risk of creating problems, little
>  risk of failure at run-time. (It might help when the client
>  [=Java process] can reset the communication to a known and
>  sane start state in case of problems detected at run-time.)

Other options:

* Use a message broker such as CORBA or MQ. Perhaps the cleanest
 solution code-wise, but requires more infrastructure and gives you a
 more complicated installation.

* Communicate through a shared database. Fiddly, but can be convenient
  if the programs share a database anyway.

* REST -- have an HTTP servlet running in one program and make RESTful
  calls to it from the other. (Roughly the same as a SOAP approach,
  but if the communication is mostly command and control messages, it
  might be more convenient.)

* JNI wrapper around shared memory / memory mapped files. Very fiddly,
  very system specific, but potentially very high performance.
  (There's a discussion on using memory mapped files with java here:
  http://tinyurl.com/6oa3wej  )

* The presence of trigger / lock files in a directory. Quick and easy,
  but limited.

* Use a shared web resource / whiteboard. Quick and convenient if your
  programs do HTTP calls anyway, but requires the shared web resource
  to be in place and there's performance and latency to take into
  account.

-- 
Leif Roar Moldskred

Back to comp.lang.java.programmer | Previous | Next | Find similar | Unroll thread

Thread

Re: Interplatform (interprocess, interlanguage) communication Leif Roar Moldskred <leifm@dimnakorr.com> - 2012-02-04 02:24 -0600

csiph-web