Re: [whatwg/fetch] Deferred fetching (PR #1647)

@noamr pushed 42 commits.

bd874a2fda3b93ce10fd764a3e752a7a4c952a23  Deferred fetching
b19831df298baa9e46dc822253d3042c4c5f9f8c  nits
7c3b22d841ff9e0544d681835c5dd8a91552eb27  Update fetch.bs
ee568e9222aad8c7c61205bb67fb381c583d6dcb  Move sections around
bd6dfe9947923aec5fd8cef5be5b8bd94c3d15f8  Rename to fetchLater and backgroundTimeout
5254595acf2537d7492ff0381668834f227c6064  Fix hierarchy
2df634213585482cd496ed378aa30095e6a01ae4  Restructure to expose a boolean instead of a promise
c2d6bba77f356567a4982cb290c8344c7170eb7a  nit
bfd7d74cf862b5914461d24d9f48ac4f17167e7f  or/and
ad41aa52d87d0b9a2ee4447d4b612fe2f3d8c035  Remove spurious promise
3e95cc5ae9a72295d290ffda771a78f0a226e394  Rename backgrounded
4eb56576613f6b234845ad10f90e69e8879bac4a  Throw a few more errors
507a71b3e854895c6c9cb0cc11ed310e94b29e5a  Always set keepalive
930cbe116d11467d8c5dbc3fad5b48a8c41fd35f  Nits
a5be56cf54da46319032bfa0dd7db50b8adde132  Remove atomics, leave thread safety to implementation
3ce851698c65a7583bc126ce679c5a96ea451a8a  Throw RangeError when backgroundTimeout is negative
2d734e976512aa01977ec38ec27e33a59882e56b  Refactor out backgroundTimeout, use activationTimeout
e38ea8f62a3cbcf3ef0d8ea649a63d78b9c0e621  Throw on ReadableStream
e76efc80fa203e15960912cfb76402407968c843  Fix grammar
6833147b351bf8989a62bccf600c93a1da02d058  Several editorial changes, renamed to activationDeadline
b5ab98dc0d2acd0e6343c2ba07290923255511a0  Handle CR nits
2af495a286f100f0ac4f601369c5d3c0eae57f7e  Remove h2
672b206a2672f0fd44a2317f1366f5537bae720d  Bring back line break
0060c9e67e32c525fd0c78c4999a69dc1c0c4ae3  nit
7dac9bc78907a156bb03b075e66e901f3bf0232a  nit
103c0ed3b214313630d90d7bb0a1ba15d369f3bf  nit
c1f3b8b9768dd794cd7427fa9476c77f6044f9b1  - Rename activationDeadline to activateAfter
5b4a36b9840de45219c3a916357edf2fa9f80a9a  Throw a NotAllowedError for 3p envs
2a9e9b1e2bfc1591ee578adb2be3f98af763053f  Add top-level + per-sink quota
19a072b08cf17c5bd9ed4922c2f43bc07b820aec  Check permissions policy
9fce87157f0867b69079f09b4f795b7dd89fcb44  Narrow scope to Window
10d0d33a99240461bdc7785499bdeb71f86954b5  Remove existing NotAllowedError
8fe992f0b0e41afca9cca873b8cab458e68530e8  Fix null-body issues
37c6f28aff14301edb896d593bb4e8872df0d751  Revise based on nits
3bbca6fd96cace9ce7d7e2db4afeba3ba10bae63  Use correct dfn
2f017526148d47a2a30d0e94f1ce9f1699b8852a  Remove spurious whitespace
c6bdf743e0d92427771711ed94872a0b17f2478a  Use $
81c35ab30b4b158c635c8f5eaba57236f1d5a468  Use new quota algorithm
7147d02b0485404bc4bc7e1d47020a7a4701e850  nits
3df635f2b8d3582a870a9627be007f3daf54952f  Include url+headers in the quota
ba2878ea6152f1fd5e152de0085680c189e16055  Allow 16kb (UA-specific) even for 3p contexts
b2f065c2e1a8b5849eba15b3060560d8b8644fe3  Update for new quota policy

-- 
View it on GitHub:
https://github.com/whatwg/fetch/pull/1647/files/40793493343db38b5e16ef5584e82c4ed70ce376..b2f065c2e1a8b5849eba15b3060560d8b8644fe3
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1647/before/40793493343db38b5e16ef5584e82c4ed70ce376/after/b2>

Received on Thursday, 24 October 2024 12:58:14 UTC