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

include images for contrib/branching

Browse source
This commit is contained in:
Dustin J. Mitchell 2022-04-21 01:29:47 +00:00 • committed by Tomas Babej
parent 18e11300fd
commit 04f4d3a68e
8 changed files with 14 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

18
docs/rfcs/protocol.md
View file

@ -74,25 +74,25 @@ Each task SHALL have a 'modified' date attribute that will help resolve conflict
On sync:
- Send a 'sync' type message with the entire contents of the backlog.data, unmodified, as the message payload.
* Send a 'sync' type message with the entire contents of the backlog.data, unmodified, as the message payload.
- Receive one of the following response codes:
* Receive one of the following response codes:
- 201: This means 'no change', and there is no further action to be taken.
* 201: This means 'no change', and there is no further action to be taken.
- 200: This means 'success', and the message payload contains a set of tasks and a sync key:
* 200: This means 'success', and the message payload contains a set of tasks and a sync key:
- The formatted tasks are to be stored as-is.
* The formatted tasks are to be stored as-is.
These tasks will either be appended to the client data or will overwrite existing client data, based on the UUID of the task.
No merge logic is necessary.
- The sync key will be written to the backlog.data file, overwriting the previous contents, such that it will now contain only one line.
* The sync key will be written to the backlog.data file, overwriting the previous contents, such that it will now contain only one line.
- 301: Redirect to : found in the 'info' response header, will force the client to resubmit the request to the new server.
* 301: Redirect to : found in the 'info' response header, will force the client to resubmit the request to the new server.
- 3xx, 4xx, 5xx: The 'status' field contains an error message.
* 3xx, 4xx, 5xx: The 'status' field contains an error message.
- If the response contained any error or warning, the error should be shown to the user.
* If the response contained any error or warning, the error should be shown to the user.
This provides an opportunity for the server to announce downtime, or relocation.
If no sync key is sent, the server cannot provide an incremental delta, and so will send all task data, which should be stored as above.

BIN
docs/rfcs/week.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 11 KiB