Clients, Servers, and the Request

Lesson 8 · taught by Pip

Every page you open begins with a question. Your device asks for something, and another computer somewhere answers. That little exchange — ask, answer — is the whole shape of the web, repeated billions of times a day.

Think of ordering at a coffee counter. You walk up and ask for a small latte. The barista has the machine, the beans, and the cups; you don't. You make the request, they fill it, and they hand it back. You don't need to know how the espresso machine works to get your drink. You just need to ask clearly.

Who's who: client and server

The thing that asks is called the client. That's your phone, your laptop, your browser — the side that wants something.

The thing that answers is called the server. It's a computer that mostly sits and waits, ready to hand back what's asked of it. It holds the pages, the photos, the prices. "Server" sounds grand, but it just means "the one who serves" — like the barista behind the counter.

The same machine can play both roles at different moments, but in any single exchange the split is clean: one side asks, the other side answers. Your device almost never holds the website itself; it borrows a fresh copy each time by asking for one.

What a request actually carries

A request isn't just "give me the page." It's a small, polite note with a few specific parts.

It says what you want — a particular page or picture, named by its address. It says what kind of asking you're doing — usually "I'd like to read something," sometimes "here's some information I'm sending you," like a form. And it carries a little extra context: which browser you're using, what languages you read, and so on, so the answer comes back in a form you can use.

The server reads that note, finds what was asked for, and sends back a response — the page, plus a short status saying how it went. You've met one of those statuses already: "404" is the server's way of saying "I looked, but there's nothing here by that name."

Here's the part that surprises people: a single web page is rarely one request. Loading one article might fire off dozens — one for the text, one for each image, one for the fonts, one for the logo. Your browser quietly asks for all the pieces and assembles them into the page you see, the way a barista might pull several things together to finish one order.

This same ask-and-answer is exactly how a tool like a website chat assistant works too. Your message is a request; the answer comes back from a server that knows the business. Same conversation, different counter.

Your turn

Next time a page loads slowly, notice it's not one thing arriving — it's many small answers trickling in. Watch the text appear before the images, and you're literally seeing separate requests finish at different speeds.

Next we'll open up the request itself and read the actual language it's written in — that's HTTP, and it's how your browser turns answers into the page in front of you. 🔦