Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452)

>  @domenic's idea needs a custom ReadableByteStream for FetchAPI, and a custom ExclusiveStreamReader for Fetch API because the standard ExclusiveStreamReader doesn't care about the customized read().

I don't understand why? It needs a custom underlying source, but every type of stream has a custom underlying source, so a fetch body stream should too.

One way to phrase it (that's a bit more explicit than my code that you link to) is that the underlying source sets `bodyUsed` to `true` anytime it calls `enqueue()`.

> How about @tyoshino's old idea?

I am not sure whether that idea gives any value to developers. It just tells them that somebody once accessed the `body` property---not whether any data has been read from it.

I think we need to step back and ask what the purpose of `bodyUsed` is? How do we see developers using it?

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/452#issuecomment-70611238