From f8a1c2ce7e8d6b824ea6e5e41a02f755a49c0af4 Mon Sep 17 00:00:00 2001 From: Neil Jenkins Date: Thu, 29 Sep 2022 14:14:10 +1000 Subject: [PATCH] Client guide: don't need to page in message ids --- client-guide/jmap-client-guide.mdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/client-guide/jmap-client-guide.mdown b/client-guide/jmap-client-guide.mdown index 11d26307..7f2a8cc9 100644 --- a/client-guide/jmap-client-guide.mdown +++ b/client-guide/jmap-client-guide.mdown @@ -675,7 +675,7 @@ When you next do resync, whether that's a second or several days later, apply th ## Keeping a full copy of mail in sync -JMAP can also be used to efficiently download and keep in sync the entire set of a user's mail. To do this, you would firstly get the full set of mailboxes, then page in the full list of message ids and download the actual messages. From this point on, you would only need to get the delta updates. Presuming you also want to optimise for fetching new mail first, you could do something like when you want to get the latest updates: +JMAP can also be used to efficiently download and keep in sync the entire set of a user's mail. To do this, you would firstly get the full set of mailboxes, then fetch the full list of message ids, and finally download (in batches) the actual messages. From this point on, you would only need to get the delta updates. Presuming you also want to optimise for fetching new mail first, you could do something like when you want to get the latest updates: ```json [