Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Stubs and Security

 
Matt DeLacey
Ranch Hand
Posts: 318
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hey All:
I know this has been addressed before, but it's unclear to me what the consensus was. Could those who have passed the exam comment on whether they feel it is necessary to download the RMI stub, or if you can just include it on the client side? Also, did you all have a security file or a security manager. Mine works without either but it's a little convoluted to set up, so I thought I might set permissions in a file or have a securitymanager. Any thoughts on this?
With Respect,
Matt DeLacey
 
Rahul Rathore
Ranch Hand
Posts: 324
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Matt
There is no one correct way or one best way. You can decide to choose any of the following RMI system configurations (Specified in the JGuru tutorial):-
1. CLOSED: All classes used by clients and the server must be located on the respective JVM and referenced by the CLASSPATH environment variable. NO dynamic class loading is supported.
2. SERVER BASED: A client applet is loaded from the server's CODEBASE alongwith supporting classes. This is similar to the way applets are loaded from the same HTTP server that supports the applet's web page.
3. CLIENT DYNAMIC: The primary classes are loaded by referencing the CLASSPATH environment variable of the JVM for the client. 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 server.
4. SERVER DYNAMIC: The primary classes are loaded by referencing the CLASSPATH environment variable of the JVM 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.
5. 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.
6. BOOTSTRAP SERVER: In this configuration all 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.
I have adopted the CLOSED approach because it is simpler. It does not need running of a HTTP/FTP server.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic