The Internet vs. the Web

Here's a sentence that sounds wrong and is completely true: the web is not the internet. People swap the words daily and the world keeps turning, but the difference is real, it's the door into this whole unit — and once you see it, a dozen other things snap into focus.

Roads and what drives on them

Everything you built across Units 1 and 2 — signals, packets, addresses, ports, the router relay — is the internet: the infrastructure that moves parcels between any two devices on earth. In this unit's city, the internet is the roads: asphalt, signs, sorting offices. The roads don't care what the trucks carry.

The web is one thing that drives on them: the world of pages and links you reach through a browser. One service among many — because look at the rest of the traffic on the same roads: email, video calls, online games, streaming, app syncing, messaging. None of those is "the web"; a video call doesn't involve a page. All are different vehicles on the same asphalt, and every one of them moves, underneath, as the addressed, numbered parcels you already understand. The web happens to be the most famous vehicle — it arrived in the early 1990s, decades after the roads — and it made the roads famous with it. Hence the blur.

Protocols: the rules of the road

So how do all these services share one network without chaos? The same way traffic shares a city: agreed rules. A rule set that lets two machines understand each other is called a protocol — an agreement, published for all, saying exactly how a conversation goes: who speaks first, what a request looks like, what a valid reply is, what happens when something's malformed.

The mapped analogy, part by part: a protocol is to machines what "drive on the right, stop at red, signal before turning" is to drivers. Not a suggestion — the shared convention that lets total strangers cooperate at speed without negotiating. A phone assembled in Ethiopia converses flawlessly with a server racked in Tokyo, built by companies that never met, because both follow the published rules to the letter. Machines are marvelous rule-followers; protocols are the whole trick of interoperability.

You've already met protocols without the name, and now they line up: IP — the addressing-and-delivery rules of Unit 2 (the "P" was "Protocol" all along). DHCP — the front-desk check-in script, a four-line protocol verbatim. DNS — the phone-book question-and-answer rules. Each service on the roads brings its own protocol on top of those shared ones: email has one, video calls have theirs.

And the web's own protocol — the rules for asking for pages and answering with them — has a name you've seen at the front of every address you've ever typed: HTTP. Those four letters are the statement "this conversation follows the web's rules." It's the reason a server at door 443 knows precisely what your browser will say and how to answer it.

What those rules actually say — the shape of an ask, the shape of an answer, and the meaning of the web's most famous three-digit number — is the next lesson. The roads are built; let's learn to talk.