Re: [fetch] Aborting a fetch (#27)

Not that this is a good argument on its own, but `XMLHttpRequest` provides an `abort()` method.  I don't want to see *any* incentive to keep using XHR.

The consequence of not providing an abort here is that resources will be wasted on requests that don't matter.  This can seriously harm performance, as well as being wasteful.

This came up in the discussion of media streaming scenarios (i.e., MPEG DASH) yesterday at the IETF HTTP meeting.  We didn't do a deep analysis, but it was considered important to have an explicit mechanism for cancelling a request if it was determined that network conditions had changed to the point that the current bitrate was unsustainable.

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