CSE Roadmap

Core tier · about 3 hours · 8 parts

Part 2 of 8 · 1 min read

The journey in one picture

The five steps from typing an address to seeing a page, and the idea of a round trip.

Think of sending a letter and waiting for a reply. First the sender looks up the street address in a phone book. Then a postal worker agrees with the receiver that letters will be exchanged. Then both sides agree on a secret code, so that no one in the middle can read the letters. Only then does the sender post the actual question and wait for the answer.

A web request follows exactly these steps.

  1. Find the address. The browser turns a name such as www.example.com into an IP address. This is DNS.
  2. Open a reliable channel. The browser and the server agree to talk, using TCP.
  3. Make it private. They agree on secret keys, using TLS.
  4. Ask. The browser sends an HTTP request.
  5. Answer. The server sends an HTTP response.

Round trip

A round trip is the time a message needs to go from one machine to another and for the reply to come back. It is often written RTT, for round trip time.

Example: if a message takes 50 milliseconds to reach a server and 50 milliseconds to return, the round trip time is 100 milliseconds.

A round trip is the unit of waiting on the network. Computing is fast. Waiting for the other side is slow. Counting round trips tells where the time goes.

Protocol

A protocol is an agreed set of rules for how two machines talk: the order of messages, their format and what each one means.

Example: HTTP is the protocol browsers and web servers use for requests and responses.

Check yourself:

  • Which step of the five makes the connection private?
  • What does a round trip measure?