taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 7a35e8575907ec7cd120721d6a6ffbbd5fedcba3
parent d1aecb3344e5ade5ca10f483a51eb58b0203c7f2
Author: Florian Dold <florian@dold.me>
Date:   Thu, 16 Feb 2023 20:06:20 +0100

more transitions

Diffstat:
Mdesign-documents/037-wallet-transactions-lifecycle.rst | 7+++++--
1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/design-documents/037-wallet-transactions-lifecycle.rst b/design-documents/037-wallet-transactions-lifecycle.rst @@ -143,6 +143,8 @@ States and transitions: * ``[action:abort] => aborting(delete-purse)``: The user aborts the P2P payment. The wallet tries to reclaim money in the purse. * ``[purse-timeout] => aborting(refresh)``: The other party was too slow. * ``[poll-success] => done``: The other party has accepted the payment. + * ``[poll-error] => ??``: The exchange claims that there is a permanent error regarding the purse. XXX: Do we continue + retrying? What do we do? * ``aborting(delete-purse)`` @@ -156,8 +158,9 @@ States and transitions: * ``aborting(refresh)`` - * ``[processed] => aborted)``: Aborting was successful, money was reclaimed - * ``[action:give-up] => failed``: XXX will this abort the refresh session? + * ``[processed-success] => aborted)``: Refresh group finished. Aborting was successful, money was reclaimed + * ``[processed-failed] => failed)``: Refresh group failed to complete with a permanent error. + * ``[action:give-up] => failed``: XXX will this abort the refresh session or just orphan it? * ``done``