taler-docs

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

commit f2d880840ff04dd5b050cf9cb2ae8a8504242f30
parent c274498534e64226cb6face265452278ad76402c
Author: Florian Dold <florian.dold@gmail.com>
Date:   Tue, 12 Jan 2016 15:47:56 +0100

shared presence awareness protocol

Diffstat:
Mintegration-bank.rst | 21---------------------
Mintegration-general.rst | 18+++++++++++++++++-
2 files changed, 17 insertions(+), 22 deletions(-)

diff --git a/integration-bank.rst b/integration-bank.rst @@ -13,27 +13,6 @@ Currently the following functionality is supported: For JavaScript code examples, see :ref:`communication`. --------------- -Presence Query --------------- - -The bank website queries the wallet's presence by sending a ``taler-wire-probe`` event. The -event data should be `null`. - -If the wallet is present and active, it will respond with a ``taler-wallet-present`` event. - -------------------- -Change Notification -------------------- - -While the user agent is displaying a bank website, the user might deactivate or -re-activate the wallet. A bank website *should* react to those events, and -indicate to the user that they should (re-)enable if necessary. - -When the wallet is activated, the ``taler-wallet-load`` event is sent -by the wallet. When the wallet is deactivated, the ``taler-wallet-unload`` event -is sent by the wallet. - ------------------------- Reserve Creation Request ------------------------- diff --git a/integration-general.rst b/integration-general.rst @@ -11,8 +11,24 @@ on the bank website's ``HTMLDocument``. DOM events used by Taler have the prefix ``taler-``. -.. _communication: +------------------------- +Wallet Presence Awareness +------------------------- + +The bank website queries the wallet's presence by sending a ``taler-probe`` event. The +event data should be `null`. + +If the wallet is present and active, it will respond with a ``taler-wallet-present`` event. +While the user agent is displaying a website, the user might deactivate or +re-activate the wallet. A Taler-aware *should* react to those events, and +indicate to the user that they should (re-)enable the wallet if necessary. + +When the wallet is activated, the ``taler-wallet-load`` event is sent +by the wallet. When the wallet is deactivated, the ``taler-wallet-unload`` event +is sent by the wallet. + +.. _communication: ---------------------- Communication Example ----------------------