commit 85395bdf23dd9542f7cb15071c9faab69ac9e259
parent 0e4795c27cade8b906133327955e5edcc8aaad56
Author: Marcello Stanisci <marcello.stanisci@inria.fr>
Date: Wed, 16 Nov 2016 22:49:24 +0100
Referencing get_to_backend()
Diffstat:
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/php/doc/tutorial.texi b/php/doc/tutorial.texi
@@ -215,7 +215,9 @@ increasing series of transaction IDs to avoid a chance of collisions.
Transaction IDs must be in the range of @math{[0:2^{51})}.
The function @code{post_to_backend} is shown below; we will use it
-again in other examples:
+again in other examples. Note also the function @code{get_to_backend},
+which is in charge of performign HTTP GET requests to the backend;
+it will be used by the back office script, see @ref{Back-office-integration}.
@smallexample
@verbatiminclude ../backend.php
@@ -333,14 +335,14 @@ wire transfers which paid back transaction @code{tid}. For
simplicity, the list will report only two values: the wire transfer
identifier and the date when the transfer occurred. Nonetheless,
the data returned by the backend contains more information that
-can be shown to the user.
+can be shown to the user. Note that the function @code{get_to_backend}
+is shown in the previous chapter.
As of @code{track-transfer.php}, see below the code sample, we
first check if the user
submitted all the parameters, and then we forward the request to
the backend, that in turn will request this information from the
exchange.
-@c FIXME /show/refer to/ get_to_backend()
Note the case when HTTP status code @code{402} is returned: due to
extra checks that the backend does against the data returned by the
exchange, the backend detected some inconsistency in the exchange's
