From bacb79302a7a193b4b92c97a33d35cb40034bf02 Mon Sep 17 00:00:00 2001 From: "Dustin J. Mitchell" Date: Sun, 21 Jan 2024 22:13:10 -0500 Subject: [PATCH] Change 'should' to 'may' in server snapshot requirements (#3256) For an object store backend, none of the suggestions in this paragraph make much sense. "May" is much softer, in terms of https://datatracker.ietf.org/doc/html/rfc2119. And in particular, the cloud server implementation does not do any of these things. --- taskchampion/docs/src/sync-protocol.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/taskchampion/docs/src/sync-protocol.md b/taskchampion/docs/src/sync-protocol.md index b21d7582f..98caf24e3 100644 --- a/taskchampion/docs/src/sync-protocol.md +++ b/taskchampion/docs/src/sync-protocol.md @@ -102,7 +102,7 @@ The request contains the following: * version ID at which the snapshot was made, and * encrypted snapshot data. -The server should validate that the snapshot is for an existing version and is newer than any existing snapshot. +The server may validate that the snapshot is for an existing version and is newer than any existing snapshot. It may also validate that the snapshot is for a "recent" version (e.g., one of the last 5 versions). If a snapshot already exists for the given version, the server may keep or discard the new snapshot but should return a success indication to the client.