- From: Pauan <notifications@github.com>
- Date: Sat, 12 Oct 2019 02:29:50 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 12 October 2019 09:29:53 UTC
@Mouvedia "Not receiving another chunk" is "nothing". That's the point: you have not received the data, and the server has not sent the data, so you have to sit there with nothing while you wait for the server to send the data. I'm not sure what you're arguing for. I have always argued that the timeout should include the body (in most situations), which is exactly what my `with_timeout` does. The problem with making `timeout` native to `fetch` is that you might *not* retrieve the body, you might call `fetch` solely to check the headers. So in that case the `timeout` *shouldn't* take into account the body. So how does `fetch` know whether the timeout should take into account the body or not? The `with_timeout` function does not have that problem, it makes it easy to choose whether the timeout should include the body or not. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/20#issuecomment-541306526
Received on Saturday, 12 October 2019 09:29:53 UTC