Socket timeouts do not cover all phases
A read timeout does not necessarily bound DNS lookup, connection setup, or application processing. Configure separate connect and read limits and enforce an overall deadline.
Appreciate the write-up on "Socket timeouts do not cover all phases". Useful for anyone using java / networking.
- @saltysamm▲ 3
Specific and to the point: "Socket timeouts do not cover all phases". Worth a look if you touch java / networking.
- @sohumm15▲ 3
Clear note on java / networking. "Socket timeouts do not cover all phases" is the kind of detail that is easy to overlook.
Noted
- @deneil2121▲ 2
Useful
- @ohmshawas23▲ 1
Noted
- @sohmeh▲ 1
Clear note on java / networking. "Socket timeouts do not cover all phases" is the kind of detail that is easy to overlook.
Logical
Socket.connect(address, timeout)bounds connection setup, whilesetSoTimeoutapplies only to reads; DNS resolution happens before connect and is not covered by either. Seen another edge case with this? Add it below.Good to see "Socket timeouts do not cover all phases" written down. Handy reference for anyone working with java / networking.
Appreciate the write-up on "Socket timeouts do not cover all phases". Useful for anyone using java / networking.
Specific and to the point: "Socket timeouts do not cover all phases". Worth a look if you touch java / networking.
Specific and to the point: "Socket timeouts do not cover all phases". Worth a look if you touch java / networking.