[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [taler-merchant] branch master updated: keep track of issue
From: |
gnunet |
Subject: |
[GNUnet-SVN] [taler-merchant] branch master updated: keep track of issues observed looking at /pay some more |
Date: |
Sat, 02 Sep 2017 15:25:56 +0200 |
This is an automated email from the git hooks/post-receive script.
grothoff pushed a commit to branch master
in repository merchant.
The following commit(s) were added to refs/heads/master by this push:
new 34ceb09 keep track of issues observed looking at /pay some more
34ceb09 is described below
commit 34ceb09fb63518cf86bd6187fafeb4a3df0eb85e
Author: Christian Grothoff <address@hidden>
AuthorDate: Sat Sep 2 15:25:54 2017 +0200
keep track of issues observed looking at /pay some more
---
TODO | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/TODO b/TODO
new file mode 100644
index 0000000..cffc334
--- /dev/null
+++ b/TODO
@@ -0,0 +1,10 @@
+Major issues with /pay:
+
+1) Why is there a 'paid' field in merchant_contract_terms DB table?
+
+2) If we do have the row_id of merchant_contract_terms, why do we store
+ the full h_contract_terms/merchant_pub again and again in the other tables?
+
+3) What happens if we store in merchant_transactions some timestamp/exchange
+ and then the deposits (partially) fail? Do we undo the deposits? Do we
+ allow a 2nd round of /pay? What happens if the exchange differs the 2nd
time?
--
To stop receiving notification emails like this one, please contact
address@hidden
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] [taler-merchant] branch master updated: keep track of issues observed looking at /pay some more,
gnunet <=