Theory
The layer you live in
Of all seven OSI layers, the application layer is the one you actually interact with. You never think about frames or packets, but you use email and the web every day. The application layer provides these services, email, web browsing, file transfer, directly to your programs.
This lesson covers two application-layer essentials: how email works (the accounts, mailboxes, and protocols behind it), and what a URL is, including the difference between absolute and relative URLs. Both set up the end-to-end case studies that follow.
Theory
How email works
Each email user has an account with an address (like riya@example.com) and a mailbox stored on a mail server. Sending and receiving use different protocols.
To send, your mail program uses SMTP (Simple Mail Transfer Protocol), which pushes the message out and relays it between mail servers until it reaches the recipient's server, where it is placed in their mailbox.
To read received mail, your program pulls it from your mailbox using POP3 (Post Office Protocol) or IMAP (Internet Message Access Protocol). So think: SMTP sends, POP3/IMAP retrieve. All three are application-layer protocols.
Theory
URLs: absolute vs relative
A URL (Uniform Resource Locator) is the address of a resource on the web. It comes in two forms.
An absolute URL gives the complete address: the scheme, the domain, and the full path, for example https://example.com/images/logo.png. It works from anywhere, because it spells out everything.
A relative URL gives only a partial path, for example images/logo.png, and the browser fills in the rest based on the current page's location. So on a page at https://example.com/, the relative images/logo.png resolves to the same absolute address. Relative URLs are shorter and are resolved in context.
At a glance
| Aspect | Absolute URL | Relative URL |
|---|---|---|
| Contains | The full address (scheme + domain + path) | Only a partial path |
| Example | https://example.com/images/logo.png | images/logo.png |
| Works from | Anywhere, it is complete | Resolved against the current page's location |
| Best for | Linking to other sites | Linking within the same site |
Quiz
In an email system, which protocol is used to SEND a message (and relay it between mail servers)?
- POP3, because it posts the mail
- SMTP (Simple Mail Transfer Protocol), which sends and relays mail between servers
- IMAP, because it sends messages instantly
- HTTP, because email is on the internet
Show the answer
SMTP (Simple Mail Transfer Protocol), which sends and relays mail between servers
SMTP (Simple Mail Transfer Protocol) is the protocol for SENDING email and relaying it between mail servers until it reaches the recipient's mailbox. Option A is wrong despite the name 'Post Office': POP3 is used to RETRIEVE (download) mail from your mailbox, not to send it. Option C is wrong: IMAP, like POP3, is for RETRIEVING and managing received mail on the server, not sending. Option D confuses services: HTTP transfers web pages; email uses its own protocols. Remember the split: SMTP sends (pushes out and relays), while POP3 and IMAP retrieve (pull into your mail program).
Think first
Why use relative URLs instead of always writing the full address?
Absolute URLs always work. So why do web developers often use relative URLs within a site? Then tap.
Show the answer
Because relative URLs make a site PORTABLE and easier to maintain, since they do not hard-code the domain. Imagine a site with hundreds of internal links and images. If every one used an ABSOLUTE URL like https://example.com/images/logo.png, then moving the site to a new domain, or even testing it locally before launch, would break every link until you edited all of them to the new address. With RELATIVE URLs like images/logo.png, each link is resolved against WHATEVER the current page's location is, so the same pages work unchanged on the live domain, on a staging server, or on your laptop during development, the links simply point to the right place wherever the site currently lives. This makes the site far easier to move, rename, and maintain, and it keeps the markup shorter and cleaner. The trade-off is that relative URLs only make sense for links WITHIN the same site (where 'relative to here' is meaningful); to link to a DIFFERENT website you must use an absolute URL, because there is no shared context. So the practical rule is: relative for internal links (portable, tidy), absolute for external ones (complete, unambiguous). Relative URLs let a site not care what its own address is, which is exactly what makes it easy to move.
Summary
Key takeaways
- The application layer (OSI 7) provides network services directly to user programs: email, web, file transfer.
- An email user has an account/address and a mailbox on a mail server.
- SMTP (Simple Mail Transfer Protocol) sends mail and relays it between servers; POP3 and IMAP retrieve it from the mailbox.
- Remember: SMTP sends, POP3/IMAP retrieve, all application-layer protocols.
- A URL is a web address; an absolute URL gives the complete address (scheme + domain + path).
- A relative URL gives only a partial path, resolved against the current page's location; best for links within a site.
- Memory hook: SMTP out, POP3/IMAP in; absolute = full address, relative = resolved in context.