- From: Dan Ostrowski <notifications@github.com>
- Date: Wed, 26 Aug 2015 17:13:18 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
Received on Thursday, 27 August 2015 00:13:49 UTC
I wasn't proposing an abort, I don't see it as a necessity, from the outside. A timeout argument to xhr suffices which simply results in .reject being called which, in turn, works automatically with the Promise methodology. On Wed, Aug 26, 2015, 5:06 PM Timo Tijhof <notifications@github.com> wrote: > @danostrowski <https://github.com/danostrowski> How to abort a request is > relatively straight forward. (Or at least outside the scope of this issue). > > Unfortunately, it seems we're blocked on figuring out a way to expose this > feature. E.g. do we add an .abort() method to the Promise returned by > fetch()? And how does this interact with other promises after calling > .then(). See whatwg/fetch#27 <https://github.com/whatwg/fetch/issues/27>. > > — > Reply to this email directly or view it on GitHub > <https://github.com/whatwg/fetch/issues/20#issuecomment-135211602>. > --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/20#issuecomment-135214339
Received on Thursday, 27 August 2015 00:13:49 UTC