- From: Mark Nottingham <notifications@github.com>
- Date: Tue, 23 Aug 2016 23:28:27 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
Received on Wednesday, 24 August 2016 06:30:07 UTC
My first inclination is to break out some parts of HTTP-network-or-cache Fetch into new sections and then grow them.
Specifically -
* bullets 17 and 18 ("If httpRequest's cache mode is neither...", "Otherwise, if httpRequest's cache mode is either...") should be shifted to a new "HTTP Cache Lookup" section, that specifies <http://httpwg.org/specs/rfc7234.html#constructing.responses.from.caches> algorithmically.
* after bullet 19 ("If response is null, run these substeps..."), insert a new item (or reference to a new section, "HTTP Cache Storage" or similar, along the lines specified in <http://httpwg.org/specs/rfc7234.html#response.cacheability>.
If that makes sense, I'll start a branch, and probably some tests too.
Question - Is the Streams work largely done? I suspect some of the fine points here are going to need them.
--
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/373
Received on Wednesday, 24 August 2016 06:30:07 UTC