Re: Replacing JRMP with JERI
Robert DiFalco <[email protected]>
| Newsgroups | gmane.comp.java.sun.rmi |
|---|---|
| Message-ID | <[email protected]> |
If it's as lightweight (memory and processor wise) as RMIRegistry and can run in the same JVM as my agents and servers then there is no reason. It's just not a typical reggie scenario where you would have a more centralized LUS. R. -----Original Message----- From: Gregg Wonderly [mailto:[email protected]] Sent: Thursday, July 07, 2005 3:32 PM To: Robert DiFalco Cc: [email protected]; [email protected] Subject: Re: Replacing JRMP with JERI Robert DiFalco wrote: > Not sure what you mean. You mean the RMIRegistry doesn't work with JERI? > It's not pluggable and is actually a JRMPRegistry? The RMIRegistry utilizes JRMP (a.k.a. RMI1.0) which is not plugable. That's the whole reason that JERI was done. I don't know all the finer points of the RMIRegistry. I haven't used it since 1999 when I switched to Jini. But, I don't think that there is anything other than the standard entry points for RMISocketFactory replacement. That just takes care of the transport, not the invocation layer that runs on top, and is buried inside of the JRMP layer. Can you share why you can't use the Jini LUS instead of the RMIregistry? 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