Computing · Year 6 · The Global Web and Network Infrastructure · Autumn Term

The World Wide Web: Clients and Servers

Students explore how web browsers (clients) request information from web servers to display websites.

• National Curriculum Attainment Targets
• KS2: Computing - Computer Systems and Networks

About This Topic

In the client-server model of the World Wide Web, web browsers act as clients that send requests to web servers for website content. When a user enters a URL, the browser contacts the specific server hosting that site over the internet. The server responds by delivering files such as HTML for structure, CSS for styling, and JavaScript for interactivity. The browser assembles these elements to render the final webpage students see on screen. This process reveals the collaborative, distributed structure of the web.

Year 6 students meet KS2 Computing standards in computer systems and networks through this topic in the Autumn Term unit on global web infrastructure. They explain the client-server relationship, compare browser displays of the same site due to different rendering engines, and design analogies like a library where clients request books from a central catalogue. These skills build foundational understanding of data flow and prepare for topics like search engines and cybersecurity.

Active learning benefits this topic greatly since network processes happen invisibly during normal browsing. Role plays and simulations make requests and responses visible and interactive. Students gain confidence by physically enacting the model, which strengthens recall and helps them articulate concepts clearly during discussions.

Key Questions

1. Explain the relationship between a client and a server in accessing a website.
2. Compare how different web browsers might display the same website.
3. Design a simple analogy to explain how a web page is requested and delivered.

Learning Objectives

• Explain the roles of a client and a server in the process of requesting and delivering a web page.
• Compare how two different web browsers might render the same HTML and CSS code.
• Design a simple analogy that accurately represents the client-server interaction for web browsing.
• Identify the types of files (e.g., HTML, CSS, JavaScript) a server sends to a client to display a webpage.

Before You Start

Introduction to the Internet

Why: Students need a basic understanding of what the internet is and how devices connect to it before learning about the client-server model.

Basic Computer Hardware

Why: Understanding that computers (clients and servers) are physical devices is helpful for grasping the concept of network infrastructure.

Key Vocabulary

Client	A device or program, like a web browser, that requests information or services from another computer, called a server.
Server	A powerful computer that stores website files and sends them to clients when requested over a network, such as the internet.
Request	A message sent by a client to a server, asking for specific data or a service, such as a web page.
Response	The information or service sent back by a server to a client after receiving a request.
Web Browser	Software application used to access and display information on the World Wide Web, acting as the client in the web browsing process.

Watch Out for These Misconceptions

Common Misconception

Browsers store the entire internet on the device.

What to Teach Instead

Browsers request specific data from remote servers each time a page loads. Role-play activities where students act as clients fetching items from a shared storehouse clarify that local storage holds only temporary files like cache, building accurate mental models through repeated practice.

Common Misconception

Servers automatically send all website data to every browser.

What to Teach Instead

Servers respond only to targeted client requests, conserving resources. Card-based simulations let students experience selective delivery, helping them see the pull-based nature of HTTP and reducing overgeneralisation during group debriefs.

Common Misconception

All web browsers display websites identically.

What to Teach Instead

Differences arise from unique rendering engines processing the same code variably. Hands-on comparisons across browsers reveal subtle layout shifts, with peer discussions refining observations into explanations of compatibility.

Active Learning Ideas

Role Play: Client-Server Restaurant

Divide the class into clients who place orders (URLs) with waiters, who relay to kitchen servers preparing dishes (web files). Servers deliver components back through waiters for clients to assemble meals. Debrief on delays or errors to mirror real networks. Rotate roles twice.

35 min·Small Groups

Browser Comparison Hunt

Pairs access the same three websites on different browsers like Chrome and Firefox installed on class devices. They screenshot and note display differences in layout or speed. Discuss why engines like Blink or Gecko cause variations.

25 min·Pairs

Analogy Model Build

Small groups design and construct physical models, such as a post office with request letters and response parcels containing page parts. Test the model by simulating multiple requests. Present to class with explanations.

45 min·Small Groups

Request Card Simulation

Whole class uses printed cards: clients draw request cards, pass to server stations that select and return response cards with file types. Track a full cycle on worksheets, noting sequence and dependencies.

30 min·Whole Class

Real-World Connections

• When you stream a video on YouTube, your device (the client) sends a request to YouTube's servers. The servers then send back the video data, allowing you to watch it.
• Online banking websites rely on secure client-server communication. Your browser (client) sends login details to the bank's server, which verifies your identity and provides access to your account information.

Assessment Ideas

Exit Ticket

Give students a card with the terms 'Client' and 'Server'. Ask them to write one sentence explaining the job of each and one sentence describing how they work together to show a website.

Quick Check

Present students with a simple analogy, like ordering food at a restaurant. Ask: 'Who is the client? Who is the server? What is the request? What is the response?' Discuss answers as a class.

Discussion Prompt

Ask students: 'Imagine two friends visit the same website on different devices, like a tablet and a phone. Why might the website look slightly different on each one?' Guide them to consider browser differences.

Frequently Asked Questions

How do web browsers act as clients in the World Wide Web?

Web browsers serve as clients by sending HTTP requests to web servers when users enter URLs or click links. Servers process these requests and return files like HTML and images. Browsers interpret and display the content, handling tasks such as caching for speed. This model ensures efficient, on-demand access to global resources, which students can explore through simple network diagrams.

Why do different browsers sometimes show the same website differently?

Browsers use distinct rendering engines, such as Chromium's Blink or Mozilla's Gecko, which interpret HTML, CSS, and JavaScript code in slightly varied ways. Factors like default fonts or security features also influence appearance. Classroom activities comparing live sites help students document these differences and understand the need for web standards like those from W3C.

What active learning strategies work best for teaching clients and servers?

Role plays simulate clients requesting and servers delivering, making invisible processes tangible. Browser comparisons reveal real-world variations, while building physical analogies like post offices reinforces the request-response cycle. These approaches engage kinesthetic learners, promote collaboration, and improve retention as students explain concepts to peers during rotations and presentations.

What simple analogies explain how web pages are requested and delivered?

Compare it to a restaurant: the browser (client) orders a meal (web page) from the kitchen (server), which sends ingredients separately for the waiter (network) to assemble. Or use a library: clients request books by call number, and librarians retrieve specific volumes. These everyday parallels help Year 6 students grasp the targeted, step-by-step nature of web interactions without technical jargon.