Difference Between IMAP and POP3, Web vs Proxy Server, Client-Server vs P2P: Exam Tables

Four short questions keep turning up around the application layer and the opening unit of a networks course: the difference between IMAP and POP3, the difference between web server and proxy server, the difference between client-server and peer-to-peer architecture, and "define web browser with example". In TU BSc CSIT they sit in CSC263 Computer Networks, Unit 6 "Application Layer" (SMTP, POP3, IMAP, HTTP, web servers, proxy servers and caching) and Unit 1 "Introduction to Computer Network" (client-server vs peer-to-peer). In BIT the same material is in BIT254 Network and Data Communications, Unit 8 "Transport and Application Layer Protocols" and Unit 1.

This guide gives each of the three comparisons as a table followed by the explanation, then the short definition of a web browser with examples, and ends with an outline you can follow when the question is worth 5 marks or 10.

Difference between IMAP and POP3

Both are protocols that a mail client uses to fetch mail from the receiving mail server. Sending is a different job, done by SMTP. The difference is where the mail lives after you read it.

POP3 (Post Office Protocol version 3, TCP port 110, or 995 with SSL/TLS) downloads messages from the server to one device and, by default, deletes them from the server. The mailbox effectively moves to your computer. It works offline once the download is done and uses little server storage, but a second device sees an empty mailbox, and a lost disk means lost mail.

IMAP (Internet Message Access Protocol, TCP port 143, or 993 with SSL/TLS) leaves the messages on the server and lets the client view and manage them there. Folders, read and unread flags, deletions and searches are all kept on the server, so every device shows the same mailbox. The client usually fetches only headers first and downloads a message body when you open it.

In an exam, add one line saying that SMTP (port 25) pushes mail from the sender to the server while POP3 and IMAP pull it to the user.

Difference between web server and proxy server

A web server is the machine and software (Apache, Nginx, IIS) that stores web resources and answers HTTP requests for them. It is the origin of the content: when a browser asks for a page, the web server finds the file or runs the program that builds it and returns an HTTP response.

A proxy server sits between clients and servers and acts on behalf of the client. The browser sends its request to the proxy, which either answers from its own cache or forwards the request to the real web server and passes the reply back. Because it keeps copies of recently fetched objects, a proxy cuts repeated traffic and delay. It can also filter sites, log usage, and hide the client's address from the outside server. A proxy is therefore both a server (to the browser) and a client (to the web server).

A useful sentence for the caching part: when the proxy already has a fresh copy it replies without contacting the origin, and when it does not, it fetches, stores a copy and replies. A reverse proxy does the mirror job on the server side, sitting in front of web servers to share load.

Client-server vs peer-to-peer architecture

The question "can you illustrate the difference between client-server and peer-to-peer network architecture" wants a comparison plus a picture of each.

In the client-server model one or more dedicated machines, the servers, provide services and many clients request them. The server is always on, has a well-known address and holds the shared resources and the control. A web browser asking a web server for a page, or a mail client asking a mail server, is client-server. Control is central, so security, backup and administration are easier, but the server is a single point of failure and a bottleneck when many clients arrive.

In a peer-to-peer (P2P) network every computer is both a client and a server. Peers share files, printers or processing power directly with each other, with no dedicated server. It is cheap and simple for a small group, and it has no single point of failure, but security and backup are managed machine by machine, and performance suffers as the network grows. BitTorrent file sharing and a small office with a few computers sharing folders are P2P examples.

For the diagram, draw a server box in the centre with arrows from several client boxes for client-server, and a mesh of equal boxes linked to each other for peer-to-peer. The network topology picture below helps with the P2P mesh.

Define web browser with example

A web browser is application software on the client computer that requests web pages from web servers using HTTP or HTTPS, receives the HTML, CSS, JavaScript and media in the reply, and renders them as a page the user can read and interact with. It also handles the URL, keeps history and bookmarks, runs scripts, manages cookies and caches pages locally. Examples are Google Chrome, Mozilla Firefox, Microsoft Edge, Apple Safari and Opera. The browser is the client half of the web's client-server model, and a web server is the other half.

How to write it in the exam

For a 5-mark "differentiate" question, write the definition of each side in one line, then a table of five or six rows with the points above, and one example for each. Choose the rows that are most visibly different: where mail is stored and number of devices for IMAP and POP3, content versus intermediary and caching for web and proxy server, and control, cost and security for client-server and P2P.

For a 10-mark question, add the working: the SMTP, POP3 and IMAP roles for mail, the cache hit and miss path for a proxy, and a labelled diagram for the architectures. Keep the definition of a web browser to two lines with two examples.

Read the full units on the CSC263 Application Layer notes and the Introduction to Computer Network notes. BIT students can use the BIT254 Transport and Application Layer Protocols notes, and the full subject pages are CSC263 Computer Networks and BIT254 Network and Data Communications.