Abortable fetch | Blog | Chrome for Developers
The original GitHub issue for "Aborting a fetch" was opened in 2015. Now, if I take 2015 away from 2017 (the current year), I get 2. This demonstrates a bug in maths, because 2015 was in fact "forever" ago. 2015 was when we first started exploring aborting ongoing fetches, and after 780 GitHub comments, a couple of false starts, and 5 pull requests, we finally have abortable fetch landing in brows
GitHub - zenparsing/es-cancel-token: Cancel Tokens for ECMAScript
Asynchronous APIs frequently need to provide the user with some way to cancel long running or expensive operations. Some examples: A browser HTTP fetch API needs to allow the user to cancel network operations if the current request is no longer required by the user interface. A database access API needs to allow the user to cancel a long-running query when the client no longer needs the results of
cancelable-promise/Third State.md at master · domenic/cancelable-promise · GitHub
Canceled as the third state This document outlines why I think it's important for cancelation to be represented as a third promise state, alongside fulfillment and rejection. It's important to note that the discussions here are independent of how the promise gets canceled, whether via the "cancelable promise" approach or the "cancel token" approach. The question is more about once a promise gets c
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Abortable fetch · whatwg/fetch@0bcd5df
Aborting a fetch: The Next Generation · Issue #447 · whatwg/fetch
Cancelable Promises
Cancelable promises
Cancelable promises
