Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

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

Re: Interplatform (interprocess, interlanguage) communication

Show all headers | View raw

On 02/03/2012 11:52 AM, Stefan Ram wrote:

>    Sockets
>
>    This is slightly less transparent than files, but has the
>    advantage that it becomes very easy to have the two
>    processes running on different computers later, if this
>    should ever be required. Debugging should be possible
>    by a man-in-the-middle proxy that prints all information
>    it sees or by connecting to the server with a terminal.

SOAP has been mentioned, but I would also look at REST. An http post 
with an XML response although less powerful, has a wider range of 
support. Using port 80/443 to get to a server also greatly simplifies 
firewall issues when the systems are remote.

>
>    JNI
>
>    JNI might be used to access code written in C or
>    ABI-compatible languages. This should be fast, but I heard
>    that it is error prone to write JNI code and needs some
>    learning (code less maintainable)?
>
The biggest drawback to JNI (I feel) is that it opens up all the 
disadvantages of C in a Java environment. It is difficult (for me) at 
times to determine exactly where an error actually is as I use C only 
when forced to.

Jeff Coffield
www.digitalsynergyinc.com

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

Thread

Re: Interplatform (interprocess, interlanguage) communication "Jeffrey H. Coffield" <jeffrey@digitalsynergyinc.com> - 2012-02-04 08:50 -0800
  Re: Interplatform (interprocess, interlanguage) communication Arne Vajhøj <arne@vajhoej.dk> - 2012-02-04 18:29 -0500

csiph-web