W3C home > Mailing lists > Public > xml-dist-app@w3.org > June 2000

Re: Question for the Sun people

From: <spetschu@ca.ibm.com>
Date: Tue, 6 Jun 2000 14:12:43 -0400
To: xml-dist-app@w3.org
Message-ID: <872568F6.00644FAC.00@d53mta05h.boulder.ibm.com>


Not a Sun person, but I used to work for them ;-). Jini is not RPC -- at
its simplest, it is a way for objects (services) to find each other in
order to start their RPC (or whatever) conversation. Instead of locating a
server/service/object by a name, you locate it in a registry which they can
discover dynamically via multicast. The services/servers/objects get
themselves into the registry by dynamically discovering via multicast the
nearest registries. What results is a very dynamically composable system of
services/servers/objects/etc.

Think Service Location Protocol crossed with the NT Registry crossed with
mobile Java code... ;-)

hth,

- steve

"Dave Winer" <dave@userland.com> on 06/05/2000 10:26:56 PM

Please respond to "Dave Winer" <dave@userland.com>

To:   xml-dist-app@w3.org
cc:
Subject:  Question for the Sun people




I just was reviewing some of the material for the Java One conference, and
re-read the What is Jini? page..

http://www.jini.org/whatisjini.html

"Devices in a network employing Jini technology are tied together using
Java
Remote Method Invocation (RMI). By using the Java programming language, a
Jini connection architecture is secure. The discovery and join protocols,
as
well as the lookup service, depend on the ability to move Java objects,
including their code, between Java virtual machines."

Is this RPC?

And if it is, how is it different from other forms of RPC?

In other words, why are Jini and RMI cool, but XML-RPC and SOAP not?

Dave
Received on Tuesday, 6 June 2000 14:15:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:56 GMT