From 17fa66c59a2438dc99c3df44de7539546a8a2035 Mon Sep 17 00:00:00 2001 From: kegsay Date: Wed, 4 Jan 2023 16:20:48 +0000 Subject: [PATCH] Update 3885-sliding-sync-to-device.md --- proposals/3885-sliding-sync-to-device.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/proposals/3885-sliding-sync-to-device.md b/proposals/3885-sliding-sync-to-device.md index 2224d9ea..d7c3ab04 100644 --- a/proposals/3885-sliding-sync-to-device.md +++ b/proposals/3885-sliding-sync-to-device.md @@ -34,6 +34,9 @@ the `to_device` extension response: } ``` +The client MUST persist the `next_batch` value to persistent storage between requests in case the client is +killed by the OS. + The semantics of the `events` field is exactly the same as the current `/sync` implementation, as implemented in v1.3 of the Client-Server Specification. The server MUST NOT send more than `limit` events: it may send less than `limit` events if the value provided was too large.