Re: [fetch] Proposed backward-incompatible change: requiring cloning all requests/responses (#61)

I just want to note there are alternatives here.

For example, streams could track and expose a .drained state.  This is a boolean.  Its cheap.  As far as I can tell it has no practical downsides.  Its just not theoretically pure to the current vision of streams.

Obviously @domenic and I disagree here.  I just want to point it out as an option, though, before we decide to break backward compat.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/61#issuecomment-110110476