- From: Jake Archibald <notifications@github.com>
- Date: Tue, 11 Apr 2017 07:41:05 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 11 April 2017 14:41:38 UTC
jakearchibald commented on this pull request. > <li> <p>Run the following <a>in parallel</a>: - <p><a for=/>Fetch</a> <var>request</var>. + <p><a for=/>Fetch</a> <var>request</var> and let <var>ongoingFetch</var> be the ongoing fetch. That sort-of seems to be how it's spec'd already, but using language "if fetch is terminated". I agree a flag would be better. The bit I'm struggling with is that the signal abort steps are main thread, but the *ongoingFetch* is created in the "in parallel" steps. Maybe the answer is to find a way to initiate the ongoing fetch on the main thread (which would have the terminated flag), then start the actual fetching in the "in parallel" bit. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/523#discussion_r110920503
Received on Tuesday, 11 April 2017 14:41:38 UTC