merchant

commit 09c090cdb8afd5e68f13064cac80f31c55fc2c35
parent a5f4a65c223f396a8b18caa492105793e46df909
Author: Marcello Stanisci <marcello.stanisci@inria.fr>
Date:   Tue,  7 Mar 2017 21:30:50 +0100

Remove confusing comment.

Diffstat:
M
src/backend/taler-merchant-httpd_track-transaction.c
 | 
10
----------

1 file changed, 0 insertions(+), 10 deletions(-)
diff --git a/src/backend/taler-merchant-httpd_track-transaction.c b/src/backend/taler-merchant-httpd_track-transaction.c
@@ -518,16 +518,6 @@ wtid_cb (void *cls,
                               &proof_cb,
                               &pcc))
   {
-    /**
-     * Conflict semantics: when the *first* call to /track/transaction
-     * at the exchange returns, the merchant issues a call to /track/transfer
-     * (at the exchange) and when that second call returns, it updates
-     * the information for all other coins using that returned information.
-     * Thus since this function is only called as callback to /track/transaction
-     * at the exchange, then if we already know this WTID, then some coin was not
-     * accounted in what /track/transfer returned (otherwise we wouldn't have
-     * tried to track it).
-     */
     GNUNET_break_op (0);
     resume_track_transaction_with_response
       (tcc->tctx,