Internet Protocol

What are Internet Protocols?

Internet protocols are a set of standardized rules that govern how data is transmitted received and interpreted over the Internet. These protocols ensure that devices and networks, regardless of their underlying hardware or software, can communicate effectively and reliably.

HTTP

HTTP (Hypertext Transfer Protocol) is the foundation of data communication on the World Wide Web. It defines how messages are formatted and transmitted, and how web servers and browsers should respond to requests.
Key Concepts of HTTP

1. Request-Response Model: • Client (Browser) sends a request to the server. • Server processes the request and sends a response back.

2. Stateless Protocol: • HTTP does not retain session information between requests. Each request is independent.

State less protocol

A stateless protocol is a communication protocol where each request from a client to a server is treated as an independent transaction. This means the server does not retain any information about the client's previous requests. Each request must include all the information necessary for the server to process it.

Key Features of Stateless Protocols:

1. Scalability

2. Fault Tolerance

3. Simplicity

   ---

   Session

   A session is a temporary interaction between a client (user) and a server that is established to maintain stateful communication for the duration of the interaction. It allows the server to remember the user’s actions or data across multiple requests during a period of time, even in a stateless protocol like HTTP.

1. State Management: Sessions help maintain information about a user across multiple requests (e.g., login status, shopping cart contents).

2. Session ID: A unique identifier (often stored as a cookie, URL parameter, or HTTP header) is assigned to the client to track the session.

3. Server-Side Storage: Session data is typically stored on the server, associated with the session ID.

4. Temporary Duration: Sessions expire after a set period of inactivity or when explicitly terminated (e.g., logging out).
   Request - Response Model

   The request-response model is a way computers communicate with each other. Here's how it works

   1. Request: One computer (the client) asks another computer (the server) for something. For example, "Show me this webpage" or "Give me this data."

   2. Response: The server receives the request, processes it, and sends back the answer. For example, the webpage's content or the requested data.

      Think of it like ordering food in a restaurant:

      1. Request: You (the client) tell the waiter (the server) what food you want.

      2. Response: The waiter brings you the food you asked for.

         HTTP/2

         HTTP/2 is an upgraded version of the HTTP (Hypertext Transfer Protocol) used for communication between clients (like browsers) and servers. It was introduced to improve the performance of web browsing and web applications compared to the earlier version, HTTP/1.1.

         Key Features of HTTP/2:

         1. Multiplexing: Multiple requests and responses can be sent over a single connection simultaneously, instead of opening multiple connections (like HTTP/1.1 does).

         2. This reduces latency because the browser doesn’t need to wait for one request to finish before sending another.

2. Header Compression:

1. HTTP/2 compresses the headers of each request and response, which reduces the amount of data that needs to be transferred.

This is particularly useful because HTTP headers can be repetitive across requests (e.g., cookies, host, etc.)
Some other jargons

1. 1. TCP (Transmission Control Protocol) • Ensures reliable delivery of data across networks. • Think of it as a delivery service that guarantees your package (data) arrives intact and in order.

      2. IP (Internet Protocol) :

         • Responsible for addressing and routing data packets between devices.

         • Like a postal system, it uses unique addresses (IP addresses) to ensure data is sent to the right location.

         3. URL (Uniform Resource Locator) • A web address that specifies the location of a resource on the Internet.

            • Example: https://www.google.com points to Google’s homepage.

         4. DNS (Domain Name System) • Translates domain names (like www.google.com) into IP addresses (like 142.250.72.46) so computers can understand and connect. • It’s like a phonebook for the Internet.

         5. Header • Part of a data packet that contains metadata, such as the sender’s address, recipient’s address, and protocol information.

            • Think of it as the “to” and “from” information on an envelope.

         6. Cache • A temporary storage area for frequently accessed data.

            • Example: Your browser stores copies of visited websites in its cache to load them faster the next time.

         7. Payload • The actual data being transmitted in a packet (e.g., a web page, a file, or an email).

            • It’s like the content inside a letter.

         8. Thank You.