From: Godmar Back (gback@cs.utah.edu)
Date: Sun Feb 07 1999 - 13:20:06 EST
Tim,
>
> I didn't even know this existed - we should definately check it out before
> doing anything else. I will take a look on Monday.
>
Here's the section on compatibility. Note the last paragraph.
- Godmar
Compatibility.
NinjaRMI is mostly source-compatible with Sun's RMI implementation
(at least in JDK1.1). What this means is that making a few small
modifications to existing code which uses Sun's RMI will allow the
code to use NinjaRMI instead. In particular:
In Sun's RMI implementation, remote objects must extend UnicastRemoteObject.
With NinjaRMI, remote objects must extend NinjaRemoteObject instead. This
is a one-line change to your code.
NinjaRMI requires the use of the ninjarmic stub compiler, rather than
Sun's rmic stub compiler.
NinjaRMI comes with its own RMI registry, which should be used instead
of Sun's. Simply run
java ninja.rmi.NinjaRegistryImpl
to start the NinjaRMI registry.
These are the only changes required to use NinjaRMI. If you want to use
the special features added by NinjaRMI, however, you'll have to make a
few additional changes (discussed below). Fortunately these are very
simple.
NinjaRMI is not compatible with Sun's RMI at a "wire" protocol level. This
means that NinjaRMI objects cannot communicate with Sun RMI objects and
vice versa. The issues here are complex and varied, and basically it is not
one of NinjaRMI's goals to be protocol-compatible with Sun RMI. I have
opted for new features and functionality rather than
backwards-compatibility with Sun.
Note that as of 23 November 1998 I intend to make a version of NinjaRMI for
the GNU Classpath project which will be source, API, and wire-protocol
compatible with Sun's version. Contact me if you're interested.
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:58:00 EDT