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

Of course, now that I think about it some more (sorry, just getting back from PTO so there are cobwebs) I don't think .drained as I defined it above completely solves the problem.

What we really need to know is if the stream is closed, all possible data read, and at least one chunk has ever been read.

That's a bit more unusual, I admit, but I still don't think it would be a problem to implement.  We could also just expose it as an algorithm concept in streams so that fetch can use it but its not available to script.

Or there is the wrapper alternative... (I don't recall why that was not adequate...)

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