taler/wallet-core
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Activity

remove redundant description

Browse Source
This commit is contained in:
Florian Dold 2016-08-16 16:48:06 +02:00
parent 9390364322
commit 62dbcba15c
1 changed files with 0 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
articles/ui/ui.tex
View File

@ -800,16 +800,8 @@ Various failure modes are considered:
% that saves Taler from being "blamed" % that saves Taler from being "blamed"
been out-of-date, updates the database and allows the user to retry been out-of-date, updates the database and allows the user to retry
the transaction. the transaction.
\item If the payment succeeded, the JavaScript on the
client side triggers effectively a ``reload'' of the fulfillment
page, triggering case (B) detailed below.
\end{itemize} \end{itemize}
{\bf (B)} Upon subsequent visits, the server detects that the payment
has already been processed and directly generates a fulfillment page
either confirming the payment, or---in the case of payments for a
digital article---transmits the digital artifact to the client.
\subsection{Bookmarks and deep links} \subsection{Bookmarks and deep links}
Taler's architecture also enables smooth use of payment Taler's architecture also enables smooth use of payment