From Shared Memory to Sockets: A Programmer’s Journey Through Network Communication

Affection

In a bustling city the narrator never meets the girl, yet they exchange countless messages by placing data in shared memory, a metaphor for inter‑process communication isolated by the operating system’s virtual memory.

The narrator longs to see her, but strict OS isolation makes it impossible to identify the correct process among thousands.

Separation

After days of yearning, the narrator asks the CPU for a description of the girl, only to be told to consult the operating system, which warns that breaking isolation could be fatal.

On Christmas Eve the girl sends a farewell note, revealing an IP address and port for future contact, hinting at a move to another “city” (computer) and introducing the concept of socket communication.

Network

Determined to reconnect, the narrator learns network programming, implements socket support, and experiences the slow three‑way TCP handshake, finally sending a greeting and receiving a delayed reply.

Through trial and error they devise an application‑layer protocol to order and format messages, highlighting the challenges of synchronizing communication over a network.

Web

When socket connections start timing out due to a firewall blocking non‑standard ports, a USB drive suggests wrapping the service as a web service using HTTP/HTTPS, which are allowed through the firewall.

The narrator switches from SOAP/WSDL to lightweight HTTP GET/POST with JSON, builds a web endpoint, and successfully contacts the girl via HTTP encapsulated in TCP/IP.

They exchange heartfelt messages, acknowledging the difficulty of their connection but celebrating the reunion.

Finally, the narrator reflects on the journey, realizing that despite the metaphorical romance, the technical lessons about shared memory, sockets, TCP, firewalls, and web services are the true takeaway.