From b0624a189ed5ea17df4a5c033a3a7bc58d200404 Mon Sep 17 00:00:00 2001 From: Ilya Kantor Date: Fri, 14 Aug 2020 19:35:28 +0300 Subject: [PATCH] minor fixes --- 5-network/06-fetch-api/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/5-network/06-fetch-api/article.md b/5-network/06-fetch-api/article.md index 6f55d1b8..413aa47b 100644 --- a/5-network/06-fetch-api/article.md +++ b/5-network/06-fetch-api/article.md @@ -219,6 +219,6 @@ It has a few limitations: - We can't send megabytes: the body limit for `keepalive` requests is 64kb. - If we need to gather a lot of statistics about the visit, we should send it out regularly in packets, so that there won't be a lot left for the last `onunload` request. - - This limit applies to all `keepalive` requests together. So we can't cheat it by creating 100 requests, each 64kb. + - This limit applies to all `keepalive` requests together. In other words, we can perform multiple `keepalive` requests in parallel, but the sum of their body lengths should not exceed 64kb. - We can't handle the server response if the document is unloaded. So in our example `fetch` will succeed due to `keepalive`, but subsequent functions won't work. - In most cases, such as sending out statistics, it's not a problem, as server just accepts the data and usually sends an empty response to such requests.