What are the different RMI system configurations possible?

Govind Seshadri

RMI systems can be configured in diverse ways:

  • Closed: All classes used by clients and the server must be located on the JRE and referenced by the CLASSPATH environment variable. No dynamic class loading is supported.
  • Server based: A client applet is loaded from the server's CODEBASE along with all supporting classes. This is similar to the way applets are loaded from the same HTTP server that supports the applet's web page.
  • Client dynamic: The primary classes are loaded by referencing the CLASSPATH environment variable of the JRE for the client. Supporting classes are loaded by java.rmi.server.RMIClassLoader from an HTTP or FTP server on the network at a location specified by the server.
  • Server dynamic: The primary classes are loaded by referencing the CLASSPATH environment variable of the JRE for the server. Supporting classes are loaded by the java.rmi.server.RMIClassLoader from an HTTP or FTP server on the network at a location specified by the client.
  • Bootstrap client: In this configuration, all of the client code is loaded from an HTTP or FTP server across the network. The only code residing on the client machine is a small bootstrap loader.
  • Bootstrap server: In this configuration, all of the server code is loaded from an HTTP or FTP server located on the network. The only code residing on the server machine is a small bootstrap loader.
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

About | Sitemap | Contact