Warning:
JavaScript is turned OFF. None of the links on this page will work until it is reactivated.
If you need help turning JavaScript On, click here.
This Concept Map, created with IHMC CmapTools, has information related to: ch5 dist case, building client and server programs: has server program: the server is a whiteboard server- it represents each shape as a remote object instantiated by a servant that implements the shape interface and holds the state of a graphical object as well as its version number, building client and server programs: has client program: any client program needs to get started by using a binder to look up a remote object reference. our client sets a security manager and then looks up a remote object reference for the remote object using the lookup operation of the RMIregistry, once obtained intital remote object reference, the client continues by sending RMI's to that remote object or to others discovered during its execution according to the needs of its applications, case study: Java RMI extends the Java object model to provide support for distributed objects in Java language contains design and implementation of Java RMI:, design and implementation of Java RMI: has java classes supporting RMI: inheritance structure of the classes supporting Java RMI servers. the class UnicastRemoteObject is every simple servant class needs to extend, it extends an abstract class called RemoteServer, which provides abstract versions of the methods required by remote servers, case study: Java RMI extends the Java object model to provide support for distributed objects in Java language contains building client and server programs:, design and implementation of Java RMI: has use of reflection: reflection used to pass info in request messages about the method to be invoked, case study: Java RMI extends the Java object model to provide support for distributed objects in Java language contains remote interfaces in Java RMI: are defined by extending an interface called remote provided in the java.rmi package. the methods must throw remote exeception parameter and result passing: parameters of a method are assumed to be input parameters and the result of a mehtod is a single output parameter, passing remote objects: when the type of a parameter or result value is defined as a remote interface, the corresponding argument or result is always passed as a remote object reference, passing non remote objects: all serializable non remote objects are copied and passed by value downloading of classes: Java is designed to allow classes to be downloaded from one virtual machine to another, two advatages- 1 there is no need for every user to keep the same set of classes in their working evironment 2 both client and server programs can make transparent use of instances of new classes when ever they are added RMIregistry: is the binder for Java RMI, an instance of RMIregistry must run on every server computer that hosts remote objects., building client and server programs: has callbacks: instead of clients polling the server to find out whether some event has occured, the server should inform its clients when ever that event does occur