World Wide Web: Master How the Web Really Works

The World Wide Web is a distributed system of interconnected resources that uses the Internet as its communication infrastructure. In this handout, we will explore hypertext, the mechanism that connects pages and resources through links, and the role of the web server in receiving HTTP requests and returning responses. We will also examine how a web application can divide processing between browser and server, and how URL structure identifies resources through components such as scheme, host, port, path, query, and fragment.

Worl Wide Web

Key points

  • World Wide Web = distributed system of resources connected through links that uses the Internet as its communication infrastructure; Web ≠ Internet.
  • Web page = document or interface built by the browser by processing resources; website = organized collection of related pages and resources.
  • HTML → content structure and meaning; CSS → presentation and layout; JavaScript → behavior, processing, and interactivity.
  • Hypertext = information structure based on links that allows users to follow non-sequential reading paths.
  • Link = connection between a selectable origin and a destination; when links also connect images, videos, audio, and interactive content → hypermedia.
  • Browser → interprets the requested address, communicates with servers, receives and processes resources, and builds the user interface.
  • Browser ↔ web server → communication primarily through HTTP requests and responses, normally protected using HTTPS.
  • Web server = software that receives HTTP requests, locates or generates requested resources, and returns the corresponding responses.
  • Static resource ≠ dynamic resource: the former is delivered as stored, while the latter is generated or assembled by the server in response to a request.
  • VPS ≠ web server: a VPS is a virtual environment that hosts programs; a web server is software that handles HTTP requests and responses.
  • Web app = software accessed through a browser; processing may occur on the device, on the server, or be distributed between both.
  • Client-side ≠ server-side: the former primarily executes processing in the browser; the latter manages significant application logic, data, and operations on the server.
  • Hybrid web application → distributes functions between browser and server; client-side and server-side therefore describe where processing takes place.
  • URL = standardized string identifying a resource; HTTP/HTTPS structure → scheme://host[:port][/path][?query][#fragment].
  • Host → network destination, potentially resolved through DNS; port → network service; path → target; query → request parameters; fragment → client-interpreted resource section.

Do you want to help me write articles like this one?

Leave a Reply

Your email address will not be published. Required fields are marked *

No responses yet

Sostieni il progetto

Tutti i materiali che condivido nascono da una convinzione molto semplice: una buona formazione non dovrebbe limitarsi a insegnare quali pulsanti premere, ma aiutare a comprendere le idee, i principi e i processi che stanno dietro agli strumenti.

Per questo dedico una parte significativa del mio tempo a studiare, organizzare e produrre contenuti gratuiti dedicati al multimedia, al design e alla comunicazione visiva. Articoli, lezioni, approfondimenti e risorse che hanno l’obiettivo di rendere accessibili argomenti spesso affrontati in modo frammentario o superficiale.

Questo lavoro richiede però tempo, ricerca e cura. Ogni guida, ogni video, ogni materiale pubblicato gratuitamente è il risultato di molte ore di studio, scrittura e revisione.
Sostenere il progetto attraverso Patreon significa permettermi di continuare a produrre contenuti educativi di qualità, mantenerli accessibili al maggior numero possibile di persone e dedicare più energie alla costruzione di una risorsa che possa essere utile a studenti, professionisti e appassionati.

Se credi che una conoscenza più profonda, rigorosa e consapevole del multimedia abbia valore, il tuo contributo non sostiene soltanto il mio lavoro: aiuta a rendere queste risorse disponibili per tutta la comunità.
Grazie per il supporto e per la fiducia.

Patreon è troppo impegnativo?

Puoi sostenermi anche con una donazione libera, senza abbonamento e senza impegno.
Anche un piccolo contributo mi aiuta a continuare a creare giochi, contenuti didattici e materiali gratuiti con più libertà.

Support the project

All the materials I share stem from a very simple conviction: good training should not be limited to teaching which buttons to press, but should help people understand the ideas, principles, and processes behind the tools.

That is why I dedicate a significant portion of my time to researching, organizing, and producing free content focused on multimedia, design, and visual communication—articles, lessons, in-depth analyses, and resources aimed at making accessible topics that are often addressed in a fragmented or superficial way.

However, this work requires time, research, and care. Every guide, video, and piece of material published for free is the result of many hours of study, writing, and revision.
Supporting the project via Patreon enables me to continue producing high-quality educational content, keep it accessible to as many people as possible, and devote more energy to building a resource that benefits students, professionals, and enthusiasts alike.

If you believe that a deeper, more rigorous, and informed understanding of multimedia is valuable, your contribution does more than just support my work: it helps make these resources available to the entire community.
Thank you for your support and trust.

Is Patreon too demanding?

You can also support me with a voluntary donation—no subscription or commitment required.

Even a small contribution helps me continue creating games, educational content, and free materials with greater freedom.