Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Powerful timeouts
See original GitHub issueCurrently there’s a single timeout option that sets a deadline for the entire request to complete.
This is suboptimal for large files and slow connections, because it doesn’t distinguish between the server not responding at all, and the file downloading reliably, but slowly.
In reality there are multiple stages of the request that can time out:
- DNS timeout
- TCP/IP connection timeout
- File upload
- Waiting for HTTP response headers
- Waiting for each chunk of HTTP response body
I’m thinking of hooking into more of these steps to allow having shorter timeouts as appropriate, e.g. DNS and TCP/IP connection never take more than a few seconds, even if the whole request needs minutes to download.
What should be the API for this? Should we try to interpret existing .timeout(2000) API in some clever way?
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
👎 for clever API interpretations and overloading. My first thought would be leave
.timeout(2000)as an alias for the entire request completing including the full body, and introduce APIs like.resolveTimeout(500),.connectTimeout(1000),.headerTimeout(3000),.chunkTimeout(4000).The MVP of response timeout seems to work well enough, so I’ll leave it at that.