[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] branch master updated: DD 50 Q&A
From: |
gnunet |
Subject: |
[taler-docs] branch master updated: DD 50 Q&A |
Date: |
Mon, 23 Oct 2023 12:39:42 +0200 |
This is an automated email from the git hooks/post-receive script.
ms pushed a commit to branch master
in repository docs.
The following commit(s) were added to refs/heads/master by this push:
new 5e748f4e DD 50 Q&A
5e748f4e is described below
commit 5e748f4e7c8884ea654425045f9cdc4e17c5cb06
Author: MS <ms@taler.net>
AuthorDate: Mon Oct 23 12:38:58 2023 +0200
DD 50 Q&A
---
design-documents/050-libeufin-nexus.rst | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/design-documents/050-libeufin-nexus.rst
b/design-documents/050-libeufin-nexus.rst
index 6f3638be..779e0b58 100644
--- a/design-documents/050-libeufin-nexus.rst
+++ b/design-documents/050-libeufin-nexus.rst
@@ -311,4 +311,7 @@ Discussion / Q&A
initiated flag in the table to true". May there be a case where the
server accepted the request, but the client never got any response (some
network issue..), and therefore didn't set the submitted flag, ending
- up in submitting the payment twice?
+ up in submitting the payment twice? Also: flagging the payment _after_
+ the bank response, may lead double-submission even if the HTTP talk ended
+ well: it suffices to crash after having received a "200 OK" response but
+ before setting the submitted flag to the database.
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.