[Top][All Lists]

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

Re: [Taler] replay and merchant backend/frontend protocol

From: Christian Grothoff
Subject: Re: [Taler] replay and merchant backend/frontend protocol
Date: Tue, 26 Jan 2016 11:19:04 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.5.0

On 01/26/2016 11:16 AM, Hartmut Goebel wrote:
> Am 26.01.2016 um 01:15 schrieb Florian Dold:
>> So it's a trade-off between customer<->merchant traffic and the
>> merchant's storage cost.
> Stupid question: Doesn't the merchant need to store the contract details
> anyway, since he needs to deliver the goods and needs the details for
> his own bookkeeping?!

Sure, but the question is if our backend logic takes care of this and
stores contracts and payment data together, or if we expect each
frontend to implement this.

The trade-off question was about _when_ the merchant stores it: only
when the contract is successful (paid), or already when it is being
generated (proposed by the merchant).  Depending on the type of
application (i.e. serving data vs. shipping goods), being lazy and only
storing 'paid' contracts can reduce database transaction volume.

Attachment: 0xE29FC3CC.asc
Description: application/pgp-keys

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

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