Hi all,
chris roffler wrote:
> Why do you want to go through all this trouble ?
>
> Why don't you just use Voyager from ObjectSpace www.objectspace.com
>
> Chris
Well, I am using voyager AND java sockets just because I need to connect
to native code and don't want to run a CORBA server.
And it really was no trouble at all to implement it!
For the Java sockets there is a rather nice example in the Java Tutorial and
under C++ it's also no problem, there are enough tools out there to build
sockets. I think my co-worker used Borld C++ Builder, for him it was just
a matter of drag an drop, and for me more or less just copy and paste ;-)
So, again, it's really no trouble, and socket communication is also quite
fast, at least for my purpose ...
enjoy
Mark
--
M a r k H o f m a n n
Department of Computer Science
University of Stellenbosch / South Africa
phone: +27-82-7449880
>
>
> -----Original Message-----
> From: Michael.Sinz [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, October 23, 1998 2:04 PM
> To: java-linux; steve
> Cc: Michael.Sinz; norm
> Subject: Re: Interprocess Communication with a Java Application
>
> On Fri, 23 Oct 1998 10:03:56 -0700, Steve Bankes wrote:
>
> >
> >I am seeking advice about interprocess communication between a
> Java application
> >and other, not necessarily Java, applications.
> >
> >I am developing the Java application under Linux but want to be
> able to run it
> >under Windows. So far I have been using Linux FIFO's (named
> pipes) rather than
> >sockets. I am using FIFO's because it is easier to write shell
> scripts that
> >will create, read from and write to FIFO's than for sockets, and
> because there
> >does not seem to be a Java internal socket; i.e there seems to be
> no Java analog
> >of AF_UNIX (UNIX internal protocols) sockets.
> >
> >So far this approach is working fine under Linux. I know nothing
> about Widows
> >or Windows programming. I am concerned how portable this will be
> to Windows.
>
> The only real IPC in Java that is platform independant is via the
> network
> I/O classes. This also happens to work rather well between
> machines, not
> just between processes. Now, it is not light weight.
>
> Windows NT has a think known as a "named pipe" the is much like a
> fifo.
> However, it requires special code to create/manage one.
> Connecting to
> one (being sender usually) is trivial and even works over the
> network
> from Windows 95 and Windows 98. However, the other end requires
> NT.
>
> Again, sockets or UDP are very handy and with 127.0.0.1 it even
> should work
> reasonably fast. (Loopback address) And, it is easy (or at least
> easier)
> to work over the network to systems of different platforms even.
> I do this
> a lot with normal sockets and RMI and serialization. (All three
> in one
> program even, but usuaully just sockets since that works almost
> everywhere)
>
> Michael Sinz -- Director of Research & Development, NextBus Inc.
> mailto:[EMAIL PROTECTED] --------- http://www.nextbus.com
> My place on the web ---> http://www.users.fast.net/~michael_sinz
>
>
