[Top][All Lists]

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

[Taler] replay and merchant backend/frontend protocol

From: Florian Dold
Subject: [Taler] replay and merchant backend/frontend protocol
Date: Mon, 25 Jan 2016 23:15:19 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1


if my understanding is correct, there is currently a deficit in the
backend/frontend protocol.

The information we get from /backend/pay is not sufficient to restore
the client's session state, since the response is empty on success.

For example in the donation shop demo, the missing information would be
the payment amount and the payment receiver ("taler", "tor", "gnunet").

Of course there are other possibilities to get this information, but for
our case it seems very convenient to just have the whole contract as a
response to /backend/pay in the frontend.

For both our demos, the information that the frontend needs from the
backend can be assembled from the contract (and if not, there should be
an "extra" field in the contract for the merchant to store
machine-readable, small pieces of information).

Now you could argue that always returning the full contract on
/backend/pay is overhead, but consider that we're talking about loopback
here in practice, and that it would make the implementation quite easy.


Christian or Marcello:  Any volunteers to implement this in the backend,
while I hack on the wallet and the shop frontend?

- Florian

reply via email to

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