Scribd
Upload
139 views

Lecture 14. Remote Object Reference

This document discusses remote object references and multicast communication in distributed systems. It defines remote object references as identifiers that uniquely specify remote objects across a distributed system. It describes how remote object references are generated to ensure uniqueness over space and time. The document also defines multicast communication as sending a single message from one process to multiple recipient processes in a transparent way. It discusses how IP multicast implements multicast communication and provides characteristics like fault tolerance and service discovery.

Uploaded by

amrita cse
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
139 views

Lecture 14. Remote Object Reference

This document discusses remote object references and multicast communication in distributed systems. It defines remote object references as identifiers that uniquely specify remote objects across a distributed system. It describes how remote object references are generated to ensure uniqueness over space and time. The document also defines multicast communication as sending a single message from one process to multiple recipient processes in a transparent way. It discusses how IP multicast implements multicast communication and provides characteristics like fault tolerance and service discovery.

Uploaded by

amrita cse
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 13

Department of

Computer Science and Engineering

2161CS136
DISTRIBUTED SYSTEMS
Unit II Process and Distributed Objects
Lecture No.14 Remote object references & Multicast
Communication
Academic Year : 2021-21(WS)
Faculty Name : Dr.M.Gokuldhev

School of Computing
Vel Tech Rangarajan Dr. Sagunthala R&D Institute of
Science and Technology
Definition
• When a client invokes a method in a remote object, an invocation message
is sent to the server process that hosts the remote object.

• This message needs to specify which particular object is to have its method
invoked. A remote object reference is an identifier for a remote object that
is valid throughout a distributed system.

• A remote object reference is passed in the invocation message to specify


which object is to be invoked.

• Remote object references are also passed as arguments and returned as


results of remote method invocations, that each remote object has a single
remote object reference and that remote object references can be
compared to see whether they refer to the same remote object. Here, we
discuss the external representation of remote object references.
The process

• Remote object references must be generated in a manner that ensures


uniqueness over space and time. In general, there may be many processes
hosting remote objects, so remote object references must be unique among
all of the processes in the various computers in a distributed system.

• Even after the remote object associated with a given remote object
reference is deleted, it is important that the remote object reference is not
reused, because its potential invokers may retain obsolete remote object
references.

• Any attempt to invoke a deleted object should produce an error rather than
allow access to a different object.
Remote object reference - uniqueness
• There are several ways to ensure that a One way is to construct a remote
object reference by concatenating the Internet address of its host computer
and the port number of the process that created it with the time of its
creation and a local object number.

• The local object number is incremented each time an object is created


in that process.
Multicast communication
• The pairwise exchange of messages is not the best model for communication
from one process to a group of other processes, which may be necessary, for
example, when a service is implemented as a number of different processes
in different computers, perhaps to provide fault tolerance or to enhance
availability.
• A multicast operation is more appropriate – this is an operation that sends a
single message from one process to each of the members of a group of
processes, usually in such a way that the membership of the group is
transparent to the sender. There is a range of possibilities in the desired
behaviour of a multicast.
• The simplest multicast protocol provides no guarantees about message
delivery or ordering.
• Multicast messages provide a useful infrastructure for constructing
distributed systems with the following characteristics:
Multicast - characteristics

1. Fault tolerance based on replicated services


2.Discovering services in spontaneous networking
3.Better performance through replicated data
4. Propagation of event notifications
IP multicast – An implementation of multicast
communication
• IP multicast • IP multicast is built on top of the Internet Protocol (IP).
Note that IP packets are addressed to computers – ports belong to the TCP
and UDP levels.

• IP multicast allows the sender to transmit a single IP packet to a set of


computers that form a multicast group.

• The sender is unaware of the identities of the individual recipients and of


the size of the group. A multicast group is specified by a Class D Internet
address that is, an address whose first 4 bits are 1110 in IPv4
IP multicast – An implementation of multicast
communication
• Being a member of a multicast group allows a computer to receive IP
packets sent to the group.

• The membership of multicast groups is dynamic, allowing computers to


join or leave at any time and to join an arbitrary number of groups.

• It is possible to send datagrams to a multicast group without being a


member.
Details are specific to IPv4

Multicast routers:
•IP packets can be multicast both on a local network and on the wider Internet.
Local multicasts use the multicast capability of the local network, for example,
of an Ethernet. Internet multicasts make use of multicast routers, which
forward single datagrams to routers on other networks, where they are again
multicast to local members.

•To limit the distance of propagation of a multicast datagram, the sender can
specify the number of routers it is allowed to pass – called the time to live, or
TTL for sh.ort
Details are specific to IPv4

• Multicast address allocation:


Class D addresses (that is,addresses in the range 224.0.0.0 to
239.255.255.255) are reserved for multicast traffic and managed globally
by the Internet Assigned Numbers Authority (IANA).
Partitioning of this address space into a number of blocks, including:
• Local Network Control Block (224.0.0.0 to 224.0.0.225), for multicast traffic
within a given local network.
• Internet Control Block (224.0.1.0 to 224.0.1.225).
• Ad Hoc Control Block (224.0.2.0 to 224.0.255.0), for traffic that does not fit
any other block.
• Administratively Scoped Block (239.0.0.0 to 239.255.255.255), which is
used to implement a scoping mechanism for multicast traffic (to constrain
propagation).
Failure model for multicast datagrams

• Datagrams multicast over IP multicast have the same failure characteristics


as UDP datagrams – that is, they suffer from omission failures.
• The effect on a multicast is that messages are not guaranteed to be
delivered to any particular group member in the face of even a single
omission failure.
• That is, some but not all of the members of the group may receive it. This
can be called unreliable multicast, because it does not guarantee that a
message will be delivered to any member of a group
Java API
Any queries??

• If not, Thank you and stay safe.

You might also like