Scribd
Upload
84 views11 pages

Remote Object Invocation

This document discusses remote object invocation in distributed systems. It covers key topics such as compile-time and run-time objects, binding clients to objects, implicit and explicit binding, implementation of object references, and static versus dynamic remote method invocation. Parameter passing is also discussed in terms of passing by reference or value.

Uploaded by

Kranthi Pidathala
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
84 views11 pages

Remote Object Invocation

This document discusses remote object invocation in distributed systems. It covers key topics such as compile-time and run-time objects, binding clients to objects, implicit and explicit binding, implementation of object references, and static versus dynamic remote method invocation. Parameter passing is also discussed in terms of passing by reference or value.

Uploaded by

Kranthi Pidathala
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 11

REMOTE OBJECT INVOCATION

Distributed objects Remote Method Invocation

DISTIBUTED OBJECTS
Object encapsulates data, the state, and the operations on those data, the methods. The separation between interfaces and the objects implementing these interfaces is crucial for distributed systems.

Common organization of a remote object with client-side

COMPILE-TIME VS RUN-TIME OBJECTS


compile-time objects, are directly related to language-level objects supported by Java and C++. The interfaces can be compiled into client-side and server-side stubs that permit Java objects to invoked by a remote machine. Dependent on particular programming language.

COMPILE-TIME VS RUN-TIME OBJECTS


For run-time objects, the implementation is left open, this allows an application to be constructed from objects written in multiple languages. It uses object adapters that give implementations of an object appearance.

BINDING A CLIENT TO AN OBJECT


Distributed objects usually support system-wide object references Object reference must bind to the referenced object before invoking any of its methods. The binding can be implicit or explicit

Implicit Binding
Distr_object* obj_ref; obj_ref = ; obj_ref-> do_something();

Explicit Binding
Distr_object objPref; Local_object* obj_ptr; obj_ref = ; obj_ptr = bind(obj_ref); obj_ptr -> do_something();

IMPLEMENTATION OF OBJECT REFERENCES

An object reference includes: The network address of the machine where the actual object resides An endpoint identifying the server that manages the object. An indication of which object an object number assigned by the server.

STATIC VS DYNAMIC RMI


Static invocation implies using object-based languages (e.g., Java) to predefine interface definitions. fobject.append(int) Dynamic invocation permits composing a method invocation at run-time. Invoke(fobject,id(append),int)

PARAMETER PASSING

The situation when passing an object by reference or by value.

You might also like