Re: [fetch] Proposed backward-incompatible change: requiring cloning all requests/responses (#61)

Well per Chrome `fetch()` would not need to implicitly clone. It seems the only problem might be `cache.put()`. Also, it's still very early days. We should be prepared to make some API changes I think. That's the whole reason we put it out there, to get feedback on what is broken etc.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/61#issuecomment-110669612

Received on Wednesday, 10 June 2015 09:27:21 UTC