分布式计算2.ppt

Jing Liu liujing@ The Distributed Object Paradigm The Distributed Object Paradigm network resources are represented by distributed objects. A process invokes one of its operations or methods, passing data as parameters to the method. The method is executed on the remote host, and the response is sent back to the requesting process as a return value. The Distributed Object Paradigm A process running in host A makes a method call to a distributed object residing on host B, passing with the call data for the parameters, if any. The method call invokes an action performed by the method on host A, and a return value, if any, is passed from host A to host B. A process which makes use of a distributed object is said to be a client process of that object, and the methods of the object are called remote methods to the client process. Local Objects vs Distributed Objects Local objects are those whose methods can only be invoked by a local process, a process that runs on the same computer on which the object exists. A distributed object is one whose methods can be invoked by a remote process, a process running on a computer connected via a network to the computer on which the object exists. Distributed Object System A distributed object is provided, or exported, by a process, here called the object server. A facility, here called an object registry, must be present in the system architecture for the distributed object to be registered. To access a distributed object, a process –an object client – looks up the object registry for a reference to the object. This reference is used by the object client to make calls to the methods. Distributed Object System Logically, the object client makes a call directly to a remote method. In reality, the call is handled by a software component, called a client proxy, which interacts which the software on the client host that provides the runtime support for the distributed object system. The runtime support i