Not every application problem is HTTP. WebSockets provide long-lived bidirectional messaging after an HTTP-based opening handshake. SMTP moves mail between mail servers and submission clients, while IMAP lets clients access mailbox state. DHCP automatically configures hosts using a small discovery and response exchange, commonly remembered as DORA.
Remember the shape, not the sentence
“Think of different city services: HTTP is a request counter, WebSocket is an open phone line, SMTP is a postal sorting system, IMAP is the mailbox viewer, and DHCP is the apartment front desk that gives you an address and basic directions.”
WebSockets
After an HTTP Upgrade-style handshake, the connection becomes a bidirectional WebSocket channel with framed messages. It is useful for realtime updates, collaboration and interactive applications.
SMTP vs IMAP
SMTP is primarily a message transfer/submission protocol. IMAP is primarily a mailbox access/synchronization protocol. A mail client commonly uses both roles for sending and reading mail.
DHCP DORA
A new client commonly broadcasts Discover, receives Offer(s), sends Request and receives ACK. The exchange can be nuanced in real deployments, but DORA is the essential conceptual sequence.
See the mechanism before you memorize it
One diagram, one causal story, one reconstruction task.
WebSockets, SMTP/IMAP, DHCP essentials — causal map
WebSocket
Handshake → protocol switch → persistent bidirectional frames.
SMTP
Client/server message submission or server/server transfer.
IMAP
Mailbox state, folders and message synchronization.
DHCP
Discover → Offer → Request → ACK.
Draw the idea yourself
Rebuild the core flow on a real canvas before moving to the worked walkthrough.
Walk the system
WebSocket
Handshake → protocol switch → persistent bidirectional frames.
SMTP
Client/server message submission or server/server transfer.
IMAP
Mailbox state, folders and message synchronization.
DHCP
Discover → Offer → Request → ACK.
Common theme
Each protocol exists because applications need a specific communication contract.
DHCP DORA
DORA is easiest to remember when linked to the problem: the client initially lacks an address, so the first message cannot depend on ordinary unicast IP connectivity.
Client → broadcast DHCPDISCOVER
Server → DHCPOFFER
Client → DHCPREQUEST
Server → DHCPACKWhat usually goes wrong
Close the tab. Rebuild it from memory.
Read the question, answer aloud, then reveal.
Why use WebSockets?Reveal answer
To maintain a persistent bidirectional messaging channel suitable for realtime interaction.
What is the core difference between SMTP and IMAP?Reveal answer
SMTP handles message submission/transfer; IMAP handles mailbox access and synchronization.
Why does DHCP start with broadcast behavior?Reveal answer
A new client may not yet have an IP configuration, so discovery must work before normal unicast IP communication is established.
Make this idea travel.
Connect it next to: devtools • dns • network-toolkit.