- From: Jeffrey Yasskin <notifications@github.com>
- Date: Wed, 03 May 2017 07:40:38 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 3 May 2017 14:41:12 UTC
1. In https://fetch.spec.whatwg.org/#fetch-method, there's no introduction for *response* other than the phrase "To process response for", so it's probably a parameter, making that block a function definition. 2. The uses of "process response", "process response end-of-body", and "process response done" in https://fetch.spec.whatwg.org/#main-fetch say to queue a task to do them, but they don't say what steps to do in them, leaving that up to someone else. 3. The definitions at https://fetch.spec.whatwg.org/#process-response don't provide steps either, making me think the intended steps are actually the ones provided by #fetch-method. 4. https://w3c.github.io/ServiceWorker/#cache-addAll and several algorithms in HTML provide other implementations of "process response", and if that's correct, then these implementations must be parameters to Fetch. -- 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/536#issuecomment-298931086
Received on Wednesday, 3 May 2017 14:41:12 UTC