diff options
author | Florian Dold <florian.dold@gmail.com> | 2016-01-12 15:47:56 +0100 |
---|---|---|
committer | Florian Dold <florian.dold@gmail.com> | 2016-01-12 15:47:56 +0100 |
commit | f2d880840ff04dd5b050cf9cb2ae8a8504242f30 (patch) | |
tree | d822f82965ef6748c4d4eb49d484adca17f8ae88 | |
parent | c274498534e64226cb6face265452278ad76402c (diff) | |
download | docs-f2d880840ff04dd5b050cf9cb2ae8a8504242f30.tar.gz docs-f2d880840ff04dd5b050cf9cb2ae8a8504242f30.tar.bz2 docs-f2d880840ff04dd5b050cf9cb2ae8a8504242f30.zip |
shared presence awareness protocol
-rw-r--r-- | integration-bank.rst | 21 | ||||
-rw-r--r-- | integration-general.rst | 18 |
2 files changed, 17 insertions, 22 deletions
diff --git a/integration-bank.rst b/integration-bank.rst index 58015cf2..c90bf042 100644 --- 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 index c73e0f87..bab13c7c 100644 --- 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 ---------------------- |