Request Protocol

Subject : Dos
Name : Raghavendra
Mca 2nd sem
Usn:3RB22MC033
Definitation of Request protocol

 A "request protocol" typically refers to the set of rules and

conventions governing how requests for information or actions
are communicated between different entities in a computer or
networked system. Request protocols are a fundamental part of
many communication systems, including those used on the
internet and within various software applications. These protocols
define the structure, format, and behavior of requests to ensure
that data or services can be exchanged effectively and efficiently.
Importance of changing bindings

 This protocol is also known as the R (request) protocol [Spector 1982]. It is used in
RPCs
 in which the called procedure has nothing to return as the result of procedure
execution
 and the client requires no confirmation that the procedure has been executed.
Since no
 acknowledgment or reply message is involved in this protocol, only one message
per call
 is transmitted (from client to server) (Fig. 4.7). The client normally proceeds
immediately
 after sending the request message as there is no need to wait for a reply message.
The
 protocol provides may-be call semantics and requires no retransmission of request
ll
 Uses of changing binding
 An RPC that uses the R protocol is called asynchronous RPC.An asynchronous RPC
 helps in improving the combined performance of both the client and the server in those
 distributed applications in which the client does not need a reply to each request.
Client
 performance is improved because the client is not blocked and can immediately
continue
 to do other work after making the call. On the other hand, server performance is
improved
 because the server need not generate and send any reply for the request. One such
 application is a distributed window system. A distributed window system, such as X-11
 [Davison et aI. 1992], is programmed as a server, and application programs wishing to
 display items in windows on a display screen are its clients. To display items in a
window.
Advantages
1. Standardization: Request protocols provide standardized rules and conventions for
communication, ensuring that different entities can communicate effectively and
consistently. This standardization facilitates interoperability between diverse systems
and application.
2. Compatibility: Request protocols enable compatibility between a wide range of
devices, software applications, and platforms. This is especially important for the
internet, where countless devices and applications need to interact seamlessly.
3. Efficiency: These protocols are designed for efficiency in terms of data transmission,
allowing for optimized use of network resources. For example, HTTP/2 and HTTP/3
include features like multiplexing and compression to reduce latency and improve
performance.
4. Security: Some request protocols incorporate security mechanisms, such as HTTPS
(HTTP Secure), which encrypts data transmitted between a client and server, enhancing
data privacy and protection against eavesdropping.
 Dis-advantages
1. Overhead: Request protocols often introduce overhead in terms of additional data (headers, metadata)
that need to be transmitted with each request. This can impact bandwidth usage, especially in high-
frequency or high-volume communications.
2. Complexity: Some request protocols can be complex to implement and maintain. For example, setting
up and configuring secure versions of protocols (e.g., HTTPS) can be challenging.
3. Latency: In some cases, the use of request protocols can introduce latency, especially when multiple
requests need to be made to complete a single operation. This can impact real-time or low-latency
applications.
4. Resource Consumption: Certain request protocols can be resource-intensive, particularly on servers,
leading to increased CPU and memory usage. This is especially relevant for protocols like SMTP
when dealing with large volumes of email traffic.
Thanking You