Communication between distributed objects

COMMUNICATION BETWEEN DISTRIBUTED OBJECTS:

Various middleware languages like RMI required to make successful communication between distributed objects.

Stub and skeleton objects works as communication objects in distributed system.

RMI means remote method invocation. Whenever needed RMI invokes the methods at client and server side objects.


As shown in above diagram, in RMI communication follows the following steps:
  • A stub is defined on client side (machine A).
  • Then the stub passes caller data over the network to the server skeleton (machine B).
  • The skeleton then passes received data to the called object.
  • Skeleton waits for a response and returns the result to the client stub (machine A).
Stub:
A stub is the client side object in distributed object communication.
The stub acts as a gateway for client side objects and all outgoing requests from client side to the server-side objects.
The stub wraps or binds client object functionality & by adding the network logic ensures the reliable communication channel between client & server.
The stub can be manually or automatically generated depending on chosen communication protocol.
Skeleton:
A skeleton is the server side object in distributed object communication.
The skeleton acts as the gateway for server side objects & for all incoming clients requests.

The skeleton wraps or binds server/called object functionality & exposes it to the clients; moreover by adding the network logic ensures the reliable communication channel between clients & server. Skeletons can be manually or automatically generated depending on chosen communication protocol.

Related topics

Professor Jayesh video tutorial

Please use contact page in this website if you find anything incorrect or you want to share more information about the topic discussed above.