GothenburgBitFactory/taskwarrior
1
0
Fork 0
mirror of https://github.com/GothenburgBitFactory/taskwarrior.git synced 2025-06-26 10:54:26 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Change 'should' to 'may' in server snapshot requirements (#3256)

Browse source 
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.
This commit is contained in:
Dustin J. Mitchell 2024-01-21 22:13:10 -05:00 • committed by GitHub
parent daca37806e
commit bacb79302a
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
taskchampion/docs/src/sync-protocol.md
View file

@ -102,7 +102,7 @@ The request contains the following:
* version ID at which the snapshot was made, and * version ID at which the snapshot was made, and
* encrypted snapshot data. * 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). 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. 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.