taler-docs

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

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

give-up -> abort-force

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

diff --git a/design-documents/037-wallet-transactions-lifecycle.rst b/design-documents/037-wallet-transactions-lifecycle.rst @@ -87,7 +87,7 @@ or starts the necessary steps to actively abort the transaction (e.g. to avoid l ``[action:resume]``: Some aborted transactions may be resumed. Whether resuming is possible depends on the transaction type. -``[action:give-up]``: Giving up puts an ``aborting`` transaction into the ``failed`` state. +``[action:abort-force]``: Directly puts an ``aborting`` transaction into the ``failed`` state. Transaction Type: Withdrawal ---------------------------- @@ -154,13 +154,13 @@ States and transitions: * If purse is already merged: ``=> done`` * Otherwise: ``=> failed`` XXX: Do we still try to refresh? - * ``[action:give-up] => failed`` + * ``[action:abort-force] => failed`` * ``aborting(refresh)`` * ``[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? + * ``[action:abort-force] => failed``: XXX will this abort the refresh session or just orphan it? * ``done``