ShopLearnFluxgrid
Lonely Binary
ESP32TinkerBlockProductsFundamentalsTools
TCP and UDP
Sending without promises4
01Why two ways to send02Which device, which app03UDP: one card, one try04What can happen on the way
TCP, step by step6
05TCP starts a connection06TCP is a byte stream07ACKs, resends and waiting08Flow control: the receiver's room09Congestion: the crowded desks10Finishing, half-close, reset
Choosing and using2
11Choosing, and meeting QUIC12From the model to your ESP32
All fundamentals →
Fundamentals/TCP and UDP/Choosing and using
Chapter · TCP and UDP

Choosing and using

How to choose by what an app needs, what QUIC adds on top of UDP, and where all of this shows up on an ESP32.

2 articlesabout 8 minutesNo board required
  1. 11Choosing, and meeting QUIC4 minChoose between TCP and UDP by what the application needs when a message is lost or late, not by which one sounds fast or important. QUIC is the newer answer, built on UDP and adding streams, recovery, congestion control and TLS 1.3.
  2. 12From the model to your ESP324 minOn an ESP32, WiFiClient is TCP and WiFiUDP is UDP, and both sit on top of lwIP, IP and Wi-Fi. A successful connect proves only the TCP handshake; each layer can fail in its own way, and the way it fails tells you which one.

Start at 11 and read down — the order is the order things get easier in. Or take the one with your part in it; every article stands on its own, and links back to whatever it needs.

← Previous chapterTCP, step by step6 articlesNext chapter →One byte on one wire5 articles
Lonely Binary

From Zeros to Heroes, One Bit at a Time.

Sydney, Australia · office@lonelybinary.com

Shop
BoardsKitsSensors & InputDisplaysBest SellersWholesale
Learn
ESP32TinkerBlockProduct handbooksFundamentalsDownloadsProduct codes
Fluxgrid
Get startedCheat sheetDocsLibrary on GitHub
Help
Contact usDeliveryReturnsWarranty
© 2026 Lonely BinaryTermsRefund policy