Module 01
Module 02
Communication
1
Message oriented Communication
1. Synchronous Communication
2. Asynchronous Communication
3. Persistent Communication
4. Transient Communication
2
Message oriented Communication
1. Synchronous Communication
Client application waits after sending request
until reply comes from server
2. Asynchronous Communication
Client application continues other work after
sending request until reply comes from the
server
3
Message oriented Communication
3. Persistent communication:
Message that has been submitted for
transmission is stored by the communication
middleware as long as it takes to deliver the
message.
It is also called a store-and-forward based
delivery paradigm.
Example: Postal system, email, etc.
4
Message oriented Communication
4. Transient communication:
Messages are buffered only for small periods of time (as
long as sending/receiving applications are executing).
If the app on the other side is unavailable and when you
can’t communicate, it discards the message → does not
ensure the message sending
Example: General Transport Layer communication.
5
Message oriented Communication
(a) Synchronous RPC (b) Asynchronous RPC
6
Message oriented Communication
7
Message oriented Communication
8
Message oriented Communication
9
Persistent Asynchronous
A is the sender and B is the receiver.
A sends a message and keeps executing without blocking.
The message sent from A will take an arbitrary amount of time to
reach B.
A may or may not be running by the time the message reaches B.
Disks or multiple memory queues could be used for storage at
B’s side. There is a guarantee that the message will eventually
reach B. B receives this request and processes it then. Example:
Emails can take an arbitrary amount of time to reach, and when the
receiver reads the email, the sender might not even be running.
10
Persistent Synchronous
Here, A sends a message, and is then blocked
(depicted by the dotted line). The acknowledgement
is for receipt (not delivery/response). Because this
model is persistent, the message may stay in B’s
queue (or in any router along the way) for an
arbitrary amount of time.
Example: Messaging and chat applications; Many
messaging systems are persistent, and can tell us the
delivery status.
11
Transient Asynchronous
A sends the message and continues execution
(nonblocking). B has to be running, because if it is
not running the message will be discarded. Even if
any router along the way is down, the message will
be discarded. UDP communication is an example of
transient asynchronous communication. The
function MP I bsend() is an implementation of this.
12
Receipt-based Transient
Synchronous
A’s message to B is blocking (synchronous) until an
ack is received. This ack simply tells us that the
message was received at the other end. It does not
tell us anything about whether the process has
started.
13
Delivery-based Transient
Synchronous
A will resume running when B takes the delivery of
the message. The ack comes a little bit later than the
previous method. This is essentially asynchronous
RPC because from the perspective of an RPC, we
are not blocking for the reply.
14
Response-based Transient
Synchronous
A resumes execution upon receiving a response. That is, not only has the
message been delivered, but it has been processed and the ack comes back in
the form of a reply. This is traditional RPC. The client is blocked for the entire
duration the reply comes back.
QUESTION : When will the message get lost?
ANSWER : We assume that the network is not dropping messages here, just a
conceptual description.
QUESTION : What if the server is not even running in case f) ?
ANSWER : If the server is not running, RPC will not even go to the server
because it cannot bind to it. However if the server was bound to and then
crashed, some form of port error would be thrown.
15
Stream Oriented Communication
Types of Streams
1. Simple Stream: Single sequence of Data
2. Complex streams: Many simple streams(sub streams)
Quality of Service (QoS):
Time-dependent and other requirements are specified as quality of service (QoS).
3. The required bit rate at which data should be transported.
4. The maximum delay until a session has been set up (i.e., when an application can
start sending data).
5. The maximum end-to-end delay (i.e., how long it will take until a data unit makes it
to a recipient).
6. The maximum delay variance, or jitter.
7. The maximum round-trip delay.
22
Stream Oriented Communication
Token Bucket to enforce QoS:
Token Bucket is an OS-based method of enforcing QoS.
Although it is not used in audio/video streaming, it is
still used in many other contexts.
It is also called a Leaky Bucket Rate Regulator.
It enforces a certain bandwidth, using an OS-level
mechanism.
23
Stream Oriented Communication
RSVP(Resourse reSerVation Protocol):
26
