[fetch] Tight coupling between JS engine and browser engine (#263)

As it stands right now, the [Fetch spec](https://fetch.spec.whatwg.org) specifies that the [bodies](https://fetch.spec.whatwg.org) of both the [Request](https://fetch.spec.whatwg.org/#concept-request) and [Response](https://fetch.spec.whatwg.org#concept-response) to have a [ReadableStream](https://fetch.spec.whatwg.org/#concept-readablestream) object associated with it, which, if my spec reading is correct, is a JavaScript engine object, due to the existence of [internal slots](https://streams.spec.whatwg.org/#rs-internal-slots).

This overlaps the responsibilities of the JS engine and the browser engine - the JS engine depends on the browser engine to implement the Fetch spec, and the browser engine depends on the JS engine to implement the concept of a ReadableStream. I believe the ideal case would be to make it so that the fetch implementation is completely self-contained, i.e. only the browser engine should need to bear responsibility in handling network fetches.

---
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/263