LAN, MAN or WAN
Try itPick a network size and see how far it reaches, how fast it runs and where you meet one in real life.
Five chapters of Internet and Web Technology, rebuilt as things you can poke. Send packets down the layers, break an IRC network, post a review on a Web 2.0 page and race HTTP/1.0 against HTTP/1.1.
Pick a network size and see how far it reaches, how fast it runs and where you meet one in real life.
Switch between pure P2P, hybrid P2P and client-server, then send a request and watch the path it takes.
Step through encapsulation. Each layer on the sender adds its header, the bits cross the wire and each layer on the receiver strips its header off. Click any layer to read what it does.
Paste any URL or pick an example. The parts light up and the DNS hierarchy is read from the root.
Every URN and every URL is a URI. Decide whether each identifier names a thing or tells you where to fetch it.
Click a tier to read its role, or trace a connection from one home to another across the tiers.
Pick an organisation, then pick its job. Correct pairs lock in green.
Judge each situation against the tenets of cyber ethics.
Step a message from Zul to Aina through every agent, then compare POP3 and IMAP on two devices.
Play an FTP session and see what someone sniffing the network can read. Then switch to SFTP.
An office with phone lines. Compare dedicated 64 Kbps circuits with VoIP calls on the data network.
IRC servers must form a spanning tree. Click any link to cut it and watch the network split.
Both ends act as a Network Virtual Terminal. Options are agreed with four commands. Run a negotiation.
Usenet sorts discussion into hierarchies. Decide where each post belongs.
Match each job to the protocol that does it. The port number comes along for free.
The Internet is the roads. The web is one kind of traffic on them. Click the three technologies that make the web work.
Request each page as a different visitor. One never changes. The other is built for you on the server.
Click a card, then click the box it belongs in.
Switch architectures and send a request through each one.
Each situation shows one of the ten challenges of the WWW. Spot which.
The same nasi lemak stall online in three eras. Read it in 1.0, post a review in 2.0 and let a software agent reason over it in 3.0.
Each layer builds on the one below. Click a layer to see its job.
Sort each feature into Web 1.0, 2.0 or 3.0.
Open each V, then name the V behind each Malaysian example.
Social networks are loosely structured, business systems highly structured and IoT data is machine-generated. Sort the sources.
Set the number of objects and the round trip time. Both timelines are drawn to the same scale.
Exam-style calculation questions with fresh numbers every time.
Type a domain and run the whole conversation, from the DNS lookup to closing. Try one DNS cannot find.
Build a real HTTP request, send it to a practice server and read the raw response. Log in, then visit your profile with and without the cookie to feel what stateless means.
The first digit tells you the class. Name it.
Log in to a bank over public Wi-Fi with HTTP, then with HTTPS. See what the attacker gets in each case.