[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [taler-docs] branch master updated: nfc: more tunneling
From: |
gnunet |
Subject: |
[GNUnet-SVN] [taler-docs] branch master updated: nfc: more tunneling |
Date: |
Fri, 13 Sep 2019 01:55:39 +0200 |
This is an automated email from the git hooks/post-receive script.
dold pushed a commit to branch master
in repository docs.
The following commit(s) were added to refs/heads/master by this push:
new ed0e2ed nfc: more tunneling
ed0e2ed is described below
commit ed0e2eda07dadf9fd79adf0afa6a7acedd31d929
Author: Florian Dold <address@hidden>
AuthorDate: Fri Sep 13 01:55:34 2019 +0200
nfc: more tunneling
---
taler-nfc-guide.rst | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/taler-nfc-guide.rst b/taler-nfc-guide.rst
index 1c0ecae..5056295 100644
--- a/taler-nfc-guide.rst
+++ b/taler-nfc-guide.rst
@@ -184,13 +184,16 @@ the ``taler://pay`` URI from the example above:
Request tunneling
=================
-Request tunnelling allows tunneling a (very) restricted subset of HTTP through
NFC.
+Request tunneling allows tunneling a (very) restricted subset of HTTP through
NFC.
In particular, only JSON request and response bodies are allowed.
It is currently assumed that the requests and responses fit into one APDU
frame.
For devices with more limited maximum APDU sizes, additional TIDs for segmented
tunnel requests/responsed may be defined in the future.
+A request for tunneling is initiated with TID 3 and responded to with TID 2
(see tables above). A tunneling request
+is identified by a numeric ID, which must be unique during one pairing between
reader and tag.
+
The request tunneling request/response JSON messages have the following schema:
.. code-block:: tsref
--
To stop receiving notification emails like this one, please contact
address@hidden.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] [taler-docs] branch master updated: nfc: more tunneling,
gnunet <=