[371] in java-interest
Re: General interest Question
daemon@ATHENA.MIT.EDU (Chuck McManis)
Fri Jun 16 17:39:42 1995
Date: Fri, 16 Jun 1995 14:08:50 -0700
From: cmcmanis@scndprsn.Eng.Sun.COM (Chuck McManis)
To: java-interest@java.Eng.Sun.COM, brouchou@lannion.cnet.fr
>- As far as I have understood, a "client" part of a java application
> (HotJava for instance) can ask a "server" part to send him a java portion
> of code across the network and execute it in local. In this case we can say
> that the code migration is done "on demand". Is it possible to imagine the
> invert process ? I mean that an application decide to send a java code
> (why not itself) to another guy, and execute on the other machine
> ("a la" Telescript).
> Ex : I have updated some information on my personnal database, I'd like to
> notify the changes to other machines.
There is no reason that you can't send Java objects to other machines to be
executed. In fact for the really foolhardy you can subvert the email system
to do this. If your mail system supports the notion of piping the mail message
through an executable, you can pipe it to the java interpreter and a base class
that would read the input stream, instantiate and run the classes inside.
What you can't do is protect your Java class from a potentially bogus Java
interpreter/runtime.
>- Is there any plan to port Java/Hotjava on OS/2 ?
Its not in our plans, others have expressed interest in doing one.
>- Java seems to be very WWW oriented, am I wrong ?
Yes, HotJava is very WWW oriented. Java is a pleasant to use, general purpose
language. Depending on the classes it uses it can be Web focused, editing
focused, you name it.
>- What is the relationship between Java and the Corba standard ?
Zero.
> Moreover, there are project to provide a Corba based environment for the WWW.
> Is there any plan to interface Java with Corba ?
Again, folks have been looking at this as well. In general the difference
between the CORBA stuff and the Java stuff is that the distributed objects
folks operate on a model of an object, portions of which are in a disjoint
address space. So invoking method A on object Y may require talking to object
X which is really on server XYZ. Java on the other hand currently takes a more
traditional approach to distribution, that is objects communicate between
each other using purpose built protocols. There is never any question when
a Java object is using the network to accomplish its job.
--Chuck
cmcmanis@sun.com
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
