Re: Replacing JRMP with JERI

--- Gregg Wonderly <[email protected]> wrote:

> Well, George, I was specifically trying to limit the
> discussion to just using JERI.  If you throw in the
> use of the LUS
> because you also need something for lookup besides
> RMID/RMIregistry which don't know how to use
> something besides JRMP
> over TCP, then there is obviously some other things
> to learn about.

There's the rub...if all you do is use JRMP and
rmiregistry with JERI, then what you've really done is
spent time to re-implement your RMI-based system to
behave exactly the way it used to. No swappable
transports, no (more convenient) dynamic code
downloading, etc. And, if you recall from our
conversation that got me in to the JINI pool in the
first place, no additional control over the DGC.

I see little point in moving to JERI unless you really
move to JERI, rather then just a minor
re-implementation of JRMP.

> The flexibility of the Configuration mechanism means
> that there is not a canned API with a limited set of
> methods to
> learn.  Instead, you design your configuration
> values and how your application uses them.  This is
> no different than
> using a properties file, or some other form of
> configuration though, so this shouldn't be a foreign
> concept to most Java
> developers.

I didn't go in to the configuration mechanism, because
any existing RMI app has already got a way to
configure the services. And in my own case, at least,
it's so integral that just replacing it with the JINI
config stuff is pretty much out of the question (at
least until I get around to re-architecting the
system).

> Thanks for putting together your rundown on steps to
> go through George.  Also, please spend some time
> look at the
> jini.org project, v2getsmart at
> http://v2getsmart.jini.org.  This project has all
> kinds of tutorial materials and links
> related to learning more about JERI and the related
> features in Jini2.0.

I've been through that stuff, and there is lots of
good info. But the caveat is that most of the info
relates to JINI 2.0, rather than the 2.1 beta. And if
you're on the beta and trying to get reggie to run
based on a 2.0 tutorial, you will be pulling your hair
out just as I did (hence my long section on reggie!).
Plus, there is no actual tutorial from the point of
view of an RMI programmer trying to move his system
over.

As a developer, I usually go for the beta (if it's a
significant rev) because I don't want to have to
re-learn anything once the beta is released.

Cheers,

George



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

===========================================================================
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