HTTP/2 Flow Control: Two Windows for Deciding How Much You'll Buffer
How HTTP/2 uses a connection-level and a stream-level credit window so a receiver can limit what it buffers and keep streams from blocking each other.
Wildness 2/5 · Mostly tamed
Topic · 8 stories
networking
8 stories tagged networking on AI Tamer, newest first.
TCP TIME-WAIT belongs to the side that closes first, and it is there on purpose
The endpoint that closes first waits 2xMSL in TIME-WAIT to resend its final ACK and to let old segments expire, so servers should set SO_REUSEADDR instead of tuning the wait away.
Wildness 2/5 · Mostly tamedThe WebSocket Upgrade Handshake, and Why Browsers Mask Client Frames
How the WebSocket Upgrade handshake proves a server actually understands the protocol, and why client-to-server frames are XOR-masked even over TLS.
Wildness 2/5 · Mostly tamedThe three timeouts every network call needs
A network call can hang while connecting, while waiting for the next byte, or by dribbling data forever. Connect, read and total timeouts each cover one of those, and some clients set none by default.
Wildness 1/5 · TamedA Large UDP Message May Depend on Every IP Fragment
One missing IP fragment can erase a whole UDP datagram. Path MTU discovery and application-sized messages help voice systems avoid that failure mode.
Wildness 1/5 · TamedTCP Keepalive Is Different From a Request Deadline
A Linux TCP connection can look healthy while an AI request stalls. Keepalive, user timeout, and an application deadline answer different questions.
Wildness 1/5 · TamedThe URL an Agent Fetches Can Point Inward
A user-supplied URL can make a server contact private services. Here is how server-side request forgery works and how to set safe fetch boundaries.
Wildness 3/5 · Partly tamedWebRTC and WebSockets carry voice AI audio differently
WebRTC is built for live media; WebSockets stream audio as ordered messages. Here is how the transport choice affects latency, loss, browser audio, and deployment.
Wildness 2/5 · Mostly tamed
