Vibeleaderboard
← Course overviewModule 02 · Understand the software underneath · Beta
Lesson 2.4

Module contents

Understand the software underneath

Lesson 4 of 6

How does the note reach another computer?

The corrected note has to reach the garden's shared message board, which lives on a computer somewhere else. This lesson follows a request from one computer to another and back, and explains what the reply does and does not tell you.

Numbered links identify sources. Underlined terms offer a definition without leaving the lesson.

A client asks; a server answers

When software on one computer wants something from software on another, it sends a request over a network, and the software at the other end sends back a response. The program that sends the request is the . The program that receives it, does something and answers is the . In this course, server means that software, not a machine; the computer running it is its host, the word from the previous lesson. One host can run several servers, and the same program can be a client in one exchange and a server in another.

MDN, the web documentation maintained by Mozilla, describes the pattern for the web: the client's request identifies a resource and what it wants done with it, the server processes the request, and its response carries a status and, often, content. 5 The status is a short code stating how the server handled the request: it succeeded, the resource was not found, the sender was not allowed, the server itself failed. The content is whatever was asked for or produced, such as a page, a file or a confirmation.

Follow the garden post. The message-board application on the organizer's laptop is the client. It sends a request that says, in effect, "add this text to the Saturday announcements", and includes the note. The board's server software, on its host, receives the request, adds the text to its own stored data and responds with a success status and perhaps the saved announcement. The board's stored data is now the persistent record; the laptop's copy is only what the client last saw. If the response never arrives, the client cannot tell whether the server saved the text and the reply was lost, or the request never got there. Module 8 deals with what to do in that situation. Here, notice only that the uncertainty is real and that sending again is not obviously safe.

A status reports handling, not correctness

Read the particular status before concluding that work finished. Some responses confirm a completed operation; others only acknowledge acceptance for later processing. On the web, for example, the 202 Accepted status does not promise that processing has finished or will succeed. 15 Our garden example specifies a response confirming that the post was saved. It does not mean the request was the one you meant to send. If the client sent the old 10 a.m. note because the edit was never saved, the server posts it correctly and reports success. If the request was addressed to the wrong board, the wrong board accepts it. The pattern from the first lesson recurs: an operation completed exactly as specified, and the specification did not match the intention. 5 When something looks wrong after a success, check what was actually sent and where it went before assuming the server misbehaved.

An API is the agreed way for software to ask

For a client to ask a server anything, both have to agree on how requests are phrased and what responses look like. That agreement, together with the set of operations it offers, is an , short for application programming interface. MDN's glossary defines an API as a software interface that exposes features and rules for other software to use, and points out that APIs can be local to one computer as well as reached over a network. 6 An interface here means the surface through which one piece of software uses another: the operations offered, the inputs each expects and the outputs each returns.

Three cautions keep the word useful. An API is not the internet: a program on your laptop uses an API to ask the operating system to open a file, with no network involved. An API is not an account: some APIs require credentials, which the next lesson explains, and some do not. And an API is not an AI feature: the message board's API, a weather service's API and an API for sending requests to a language model are the same kind of thing, an agreed set of operations, offered by different services. When module 5 discusses giving an assistant new capabilities, most of those capabilities turn out to be APIs of this ordinary kind.

Carry this forward

  • A client sends a request. A server, meaning software on some host, processes it and returns a response with a status and often content.
  • Read what the particular status confirms: acceptance and completion differ. Neither establishes that the request matched your intention.
  • A missing response leaves it unknown whether the server acted, so sending again is not automatically safe.
  • An API is the agreed set of operations one piece of software offers another. It may be local or networked, and it is not the same as an internet connection, an account or an AI feature.

Lesson check

The message-board client on the organizer's laptop reports "Posted successfully" after sending the Saturday note. The next day a neighbor points out that the board still shows 10 a.m. Which explanation is consistent with this lesson, and what should be checked first?

Choose an answer for each question.

This is a practice check. Answers reset when you leave this page. Results are not saved and do not place you in another module or award a qualification.

The board accepted the post because the request was allowed. What made it allowed, and what would have stopped it, is the next lesson.

Sources · Reviewed 2026-09-28
  1. 5. MDN: Client-server overview
  2. 6. MDN glossary: API
  3. 15. MDN: 202 Accepted does not establish completed processing

Sources support nearby explanations. Product details can change. Scenarios and model results are authored illustrations unless a lesson explicitly identifies a recorded execution. Module 7 identifies its offline code checks.