gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-docs] branch master updated: update spec'


From: gnunet
Subject: [taler-docs] branch master updated: update spec'
Date: Sun, 17 Nov 2019 21:00:50 +0100

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 52d0ab0  update spec'
52d0ab0 is described below

commit 52d0ab03fc6e0f80424b1a50dae33b5ae19da358
Author: Christian Grothoff <address@hidden>
AuthorDate: Sun Nov 17 21:00:48 2019 +0100

    update spec'
---
 core/api-sync.rst | 13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/core/api-sync.rst b/core/api-sync.rst
index d48577d..9af48c8 100644
--- a/core/api-sync.rst
+++ b/core/api-sync.rst
@@ -93,6 +93,9 @@ itself cannot not enforce these rules.
    database with a timestamp into the future, it must still
    increment it by the smallest possible amount when uploading an
    update.
+*  In general, the merge operation should be implemented in such a way
+   that it deals gracefully with adversarial devices from rouge
+   devices connected to the same account.
 
 It is assumed that the synchronization service is only ever accessed
 over TLS, and that the synchronization service is trusted to not build
@@ -121,12 +124,16 @@ Receiving Terms of Service
       // Fee for an account, per year.
       annual_fee: Amount;
 
+      // protocol version supported by the server,
+      // for now always "0.0".
+      version: Integer;
+
     }
 
 
 .. _sync:
 
-.. http:get:: /$ACCOUNT-KEY
+.. http:get:: /backups/$ACCOUNT-KEY
 
   Download latest version of the backup.
   The returned headers must include "Etags" based on
@@ -189,8 +196,8 @@ Receiving Terms of Service
 .. http:post:: /$ACCOUNT-KEY
 
   Upload a new version of the account's database, or download the
-  latest version.  The request must include the "Expect: 100 Continue"
-  header.  The client must wait for "100 Continue" before proceeding
+  latest version.  The request SHOULD include the "Expect: 100 Continue"
+  header.  The client then SHOULD wait for "100 Continue" before proceeding
   with the upload, regardless of the size of the upload.
 
   **Request**

-- 
To stop receiving notification emails like this one, please contact
address@hidden.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]