This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In XHR the loaded resource is immediately read into a memory buffer. Given that fetch will support streams, we have the opportunity to provide some amount of back pressure to the network. This would reduce the memory footprint in the case where content is reading the Response body very slowly. Consider providing an option to signal that the Response will be read slowly. This could be a boolean flag or perhaps a buffer size.
https://github.com/yutakahirano/fetch-with-streams/issues/22
It seems this will be handled as part of the streams integration per that GitHub issue.