- From: Jake Archibald <notifications@github.com>
- Date: Wed, 26 Jul 2017 08:03:15 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 26 July 2017 15:05:19 UTC
It seems that both Chrome & Firefox point to an item on disk when you do:
```js
const cache = await caches.open('test');
const response = await cache.match('/really-large-resource');
const blob = await response.blob();
```
Test: https://cache-memory-test.glitch.me/
This is pretty cool, as you can get a slice of the data without reading it all into memory. However, it seems to go against https://fetch.spec.whatwg.org/#concept-body-consume-body which requires reading the whole response.
We should spec the Chrome/Firefox behaviour, possibly by flagging requests/responses whose body is on disk.
--
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/569
Received on Wednesday, 26 July 2017 15:05:19 UTC