Network reliability

Prevents indefinite blocking by enforcing a maximum wait time on socket operations.

Client-server communication: connecting to a remote service that may be down; Data streaming: reading from a socket that may stop sending; Distributed systems: awaiting responses from peer nodes.

Low-level network code, Python's socket library, HTTP clients, microservices, IoT devices

set socket timeout → handle potential delays → ensure graceful fallback

• socket.settimeout()
• socket.connect()
• socket.recv()
• timeout exception
• socket.timeout

• use non-blocking sockets with select() instead of a timeout → more control but adds complexity
• use asyncio.wait_for() for async code → integrates with event loop
• set per-operation timeout via socket.setsockopt() → finer granularity but less portable

Setting timeout to zero, thinking it disables timeout but actually makes socket non-blocking → leads to unexpected EWOULDBLOCK errors; forgetting to handle socket.timeout exception → program crashes on timeout; using a timeout that is too short for expected latency → frequent unnecessary retries

socket timeout vs read timeout: socket timeout applies to the whole operation, read timeout only to recv calls; connection timeout vs overall request timeout: connection timeout covers only the handshake phase

Coming from JavaScript: assuming fetch's timeout option works like socket timeout → fetch does not have a native timeout, you need AbortController to enforce it

• socket timeout
• network timeout
• connection handling

Do not use socket timeout when employing non-blocking I/O with explicit select/poll loops; very low timeout values can increase CPU usage due to frequent retries; timeout only affects blocking calls, not asynchronous callbacks

Ensures applications remain responsive and can recover from unresponsive peers, reducing risk of resource exhaustion.

A socket timeout is like a kitchen timer that stops cooking if the dish takes too long, preventing the pot from boiling over.

Timeout is set per socket object; changing it after a connection is established affects subsequent operations only.