⌘K
ENES
GitHub
phase~1 min de lecturaActualizado 2026-06-30#phase#clients
Esta nota todavía no está traducida, así que se muestra la fuente en inglés.

Phase 06 · Two Clients, One Protocol

The same protocol specification, implemented twice, on purpose: a terminal client in C with a non-blocking I/O loop serving keyboard input and network messages at once, and a client in TypeScript/Node with automatic reconnection and out-of-order message handling. The point isn't building the same thing twice — it's seeing exactly what a high-level runtime gives you for free versus what you had to write by hand.

Notas relacionadas

Low-LevelPhase 00 · OrientationWhere to start, what Atlas I and II you need first, and how this atlas is organized.Low-LevelPhase 01 · TCP from ScratchRaw BSD sockets to the bone — the handshake, Nagle, buffers, backpressure, and real network errors.Low-LevelPhase 02 · Design Your Own ProtocolFraming, binary serialization, versioning, and heartbeats over raw TCP — before adopting WebSocket.Low-LevelPhase 03 · WebSocket, for RealRFC 6455 implemented by hand in C — handshake, frame format, control frames, fragmentation, close.