- From: Domenic Denicola <notifications@github.com>
- Date: Sun, 15 Mar 2015 21:47:36 -0700
- To: whatwg/streams <streams@noreply.github.com>
Received on Monday, 16 March 2015 04:48:03 UTC
Right, there is a lot of discussion about how to do fetch cancellation, I think in the service worker repo. I think it is OK to (eventually) have multiple possibilities as long as they all related together. E.g. maybe `fetchPromise.cancel()` is defined as doing either (1) internal method to cancel request before headers are received; or (2) canceling the stream, and maybe (2) is exposed directly (since it is more general). Hmm. But if we allow `fetchPromise.cancel()` (or the canceller approach) then we have to decide what it does when the stream is locked. So that comes back to our original problem. --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/streams/issues/297#issuecomment-81410658
Received on Monday, 16 March 2015 04:48:03 UTC