Re: Replacing JRMP with JERI

Niclas Hedhman wrote:
> On Wednesday 06 July 2005 12:59, Gregg Wonderly wrote:
>
>>JERI technologies were originally submitted as
>>JSRs, but were rejected because of many reasons, some apparently political.
>
> Hmmm. I have not yet taken a look at JERI, although I have suspected that it
> was the JSR78 stuff... Great that the sweat I invested in 2000 to scrutinize
> that spec+RI actually got to some use.
> Does that mean that the JSR76 stuff is in Jini 2.0 as well??

There were several further developments for the features specified in both JSRs, but yes, they are both in the JERI
stack present in Jini 2.0 and later.  Anyone interested in the next generation of RMI should look at JERI.  It really
does enable a number of powerful security and transport related capabilities.  The RMI crowd, would in particular,
appreciate the fact that you can substitute HTTP vs HTTPS vs SSL vs TCP vs Kerberos transports at deployment time with a
configuration file change that uses Java code.  Thus, you can do all kinds of things to construct your configuration
with runable code, instead of having to run a tool up front to generate some kind of text configuration.

Gregg Wonderly

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff RMI-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

For a list of frequently asked RMI questions please refer to:
http://java.sun.com/j2se/1.3/docs/guide/rmi/faq.html

To view past RMI-USERS postings, please see:
http://archives.java.sun.com/archives/rmi-users.html