Mastering Jargon: How to Simplify and Understand Tough Terms

What is Jargon

Mastering Jargon: How to Simplify and Understand Tough Terms

Jargon is a special words or terms used by a people in a specific jobs, groups or field. It includes words and phrases they can be hard for other people to understand easily. while it helps expert communicate clearly it can confuse those who aren’t familiar with it.

HTTP (Hyper Text transfer protocol)

It’s like a set of rules that allows to computer and a website to talk each other and share information

for example, Raju searches your college websites. then first write the address of website like (college.com), Http helps your computer requested the page and display it for you.

Flow chart of working of HTTP

Protocol

A protocol is like a set of rules or instructions that devices follow to communicate with each other. It ensures that the information being sent form one device like a computer, laptop etc. is received and understand correctly by another device

for example: - Two people speak the same language is English and communicate with easily as same that in computer Protocol follow that rule to communicate with devices

Request - Response Model

Request - Response Model is a way that computers (or devices) to communicate with each other over a network. In simple terms, any devices send a request, and the other devices send back a response

For example: - If you go shop Ask the shopkeeper give a book (its request). The shopkeeper brings back with book (response).

Https Header & Payload

Header

Header is a piece of information sent along with a request or response. Think of it like a note or a label that provides extra details about the request or response.

Payload

Payload in HTTPS is the actual data or content being sent between the client (like a web browser) and the server.

Stateless Protocols

A stateless protocol is a type of communication where each request from a client to a server is independent and doesn’t rely on any previous requests. In simple terms, the server doesn't store or remember information from one request to the next.

For example: - you enter the store, you grab a cart and go shopping. The cashier doesn’t remember what you bought last time. You have to tell them what you want now (just like every request in a stateless protocol).

HTTP Evolution

HTTPS has evolved over time with different versions, each improving security and performance:

HTTP/1.1

HTTP/1.1: The initial version, providing basic request-response communication over a secure channel using SSL/TLS.

  1. TLS 1.0/1.1: Early versions of Transport Layer Security, enhancing encryption and secure connections.

  2. TLS 1.2: A widely used version offering stronger encryption, better performance, and support for modern security features.

  3. TLS 1.3: The latest version, further improving security by simplifying encryption, reducing handshake latency, and removing outdated cryptographic methods.

HTTPS 2 (HTTP/2) - Performance Enhancement

  1. Speed & Performance:
    HTTP/2 makes websites load faster by reducing latency. It allows multiple data streams to be sent at once, rather than one at a time, so everything is delivered quicker.

  2. Enhanced Security:
    While still using SSL/TLS for encryption, HTTP/2 also supports encryption improvements, making data even more secure than older versions.

TLS (Transport Layer Security)

TLS (Transport Layer Security) is a protocol that provides secure communication over the internet. It ensures that data sent between a client (like a web browser) and a server is encrypted, meaning it's protected from eavesdropping and tampering.

SSL (Secure Sockets Layers)

SSL (Secure Sockets Layer) is a protocol that provides a secure connection between a web browser and a website. It ensures that the information you send and receive is encrypted and safe from hackers.

Cookie

Cookies are small pieces of data stored on your computer or device by a website you visit. They help websites remember things like your preferences, login information, and other details to make your browsing experience smoother.

example: - When Raju visits his college website to download his admit card, cookies store his login information and preferences, making the process smoother by remembering his details for future visits

Flow chart of How Cookie work on browser

User Agent

Transfer Control Protocol (TCP)

Transfer → Sending of something.

Control → Having a hold over something (For example → Your life is in your control)

Protocol Rules/guidelines about something.

It basically boils down to → ‘Rules about how the sending of something will be controlled’

for example. Raju sends a letter to Ravi, who ensures it's received correctly. If the letter is lost or damaged, Raju resends it until Ravi confirms successful delivery.

File Transfer Protocol 📂(FTP)

Rules about how the sending of files will be controlled

File can be → MP3, MP4, JPG, PNG, SVG, XLS etc.

Example → Your friend told you to take chocolates (file) to his home, but if the chocolates are over 1KG (size of the file) then carry them in a jute bag instead of plastic bag. It is a protocol isn’t it!

Internet Protocol (IP) 🌐

Rules regarding how the data packets are transferred between various devices across the internet.

Data Packets → Data is transferred in small chunks across the internet. These small chunks are known as data packets.

Uniform Resource Locator (URL) 🌐

The above figure shows what a URL looks like.

Uniform → Because all of the URLs have similar structure.

Resource → The thing that you are trying to access through the internet.

Locator → It enables the browser to find your desired resource across the internet (just like the address)

It is just like the map you use to go somewhere.

Domain Name System / Server 👾

It maps the name of the domain (for example → google.com) to it’s corresponding IP Address because computers don’t interact through human readable formats across the network.

How to work DNS

  • User Request: A user enters a URL (e.g., www.rajuwebsite.com) into a browser.

  • DNS Resolver: The browser queries the local DNS Resolver to find the IP address of the URL.

  • Cache Check: The DNS Resolver checks its cache for the domain's IP address:

    • If found, it returns the result.

    • If not, it proceeds to step 4.

  • Root Server: The resolver contacts a Root DNS Server, which points it to the appropriate TLD Server (e.g., .com, .org).

  • TLD Server: The resolver queries the TLD Server, which provides the IP address of the Authoritative DNS Server for the domain.

  • Authoritative Server: The resolver contacts the Authoritative DNS Server, which provides the IP address of the requested URL.

  • Return IP: The IP address is sent back to the resolver, which forwards it to the user's browser.

  • Browser Access: The browser uses the IP address to establish a connection and fetch the website content.

Flow charts of DNS

User Datagram Protocol

UDP (User Datagram Protocol) is a lightweight, fast, and connectionless protocol used for sending data over the internet. Unlike TCP, it does not guarantee delivery, order, or error correction, making it ideal for applications where speed is more important than reliability.

Example with Raju:

Imagine Raju is hosting a cricket commentary live on his app. He sends match updates (data packets) quickly to all his friends without waiting for confirmation that everyone has received them. If someone misses an update, Raju doesn’t resend it because the next update will come quickly. This is how UDP prioritizes speed over reliability.

Quick UDP Internet Connections (QUIC)

QUIC is a modern internet transport protocol built on top of UDP to make data transfer faster, more reliable, and secure. It was designed by Google and is now widely used for applications like video streaming, online gaming, and web browsing.

Example with Raju:

Raju is watching a live cricket match online. Using QUIC, the stream starts quickly and continues smoothly, even if Raju switches from his home Wi-Fi to mobile data. QUIC ensures the stream is fast, secure, and uninterrupted.

Voice Over Internet Protocol (VOIP)

VoIP (Voice over Internet Protocol) is a technology that allows you to make voice calls using the internet instead of a regular phone line. It converts your voice into digital data and sends it over the internet to the person you’re calling.

Example with Raju:

Raju wants to call his friend Ravi, who lives abroad. Instead of using an expensive international call, Raju uses VoIP through an app like WhatsApp or Zoom. The call is clear, and it costs him nothing extra since it uses his internet connection.

Fire Wall

A firewall is like a security guard for your computer or network. It monitors and controls the flow of data coming in and going out, blocking anything suspicious or harmful, such as hackers or viruses.

Example with Raju:

Raju's computer is connected to the internet. To protect his data, he uses a firewall, which acts like a gatekeeper. If a hacker tries to sneak in or harmful data tries to enter, the firewall blocks it, keeping Raju's computer safe

Mac Address

A MAC address (Media Access Control address) is like a unique name tag for a device that connects to the internet, such as your phone, laptop, or Wi-Fi router.

Every device has its own MAC address, which helps networks identify it and send the right data to the right device. Think of it as your device’s fingerprint for communication on a network.

Conclusion

In conclusion, whether it's understanding technologies like TCP, UDP, QUIC, VoIP, or firewalls, their purpose is to make communication faster, safer, and more efficient. These tools and protocols form the backbone of modern networking, ensuring seamless connections, security, and reliability for users like Raju in everyday scenarios. Embracing these technologies helps us navigate the digital world more effectively.