Fix bikeshed errors in fetch callbacks #164
Conversation
|
@annevk I don't have a good solution for |
| 1. [=/Fetch=] |request| with the following arguments: | ||
| <dl class="compact"> | ||
| : [=fetch/useParallelQueue=] | ||
| :: True. |
There was a problem hiding this comment.
@annevk I know the fetch spec says I shouldn't need this, but my intent is to be able to do this processing without any page open.
There was a problem hiding this comment.
The tricky aspect is how we enforce any of the things that Fetch requires a client for, such as referrer and CSP. It seems you would have to obtain these ahead of time and pass them in somehow, but there's no infrastructure for that as of yet.
| :: The following steps given |chunkLength| (a number): | ||
| 1. Increment |bgFetch|'s [=background fetch/uploaded=] by |chunkLength|. | ||
| 1. [=Update background fetch instances=] for |bgFetch|. | ||
| : [=fetch/processResponse=] | ||
| :: The following steps given |response| (a [=/response=]): |
There was a problem hiding this comment.
These are pretty much just re-indentings of the previous algorithm.
|
With current implementations, once you have seen a response the request has been transmitted. You could wait for processRequestEndOfBody as well I suppose? |
No description provided.