summaryrefslogtreecommitdiff
path: root/example-essay-store.rst
diff options
context:
space:
mode:
authorMarcello Stanisci <marcello.stanisci@inria.fr>2016-03-23 13:03:21 +0100
committerMarcello Stanisci <marcello.stanisci@inria.fr>2016-03-23 13:03:21 +0100
commit26d4f610d11bcb2edca2f201341df18ecd28faa5 (patch)
treeb4ac7e443d939a8c8670e508bbac292bcd8a7bf6 /example-essay-store.rst
parent98df0140e4afaff06c310f1a3cb2e1ce506746ff (diff)
downloaddocs-26d4f610d11bcb2edca2f201341df18ecd28faa5.tar.gz
docs-26d4f610d11bcb2edca2f201341df18ecd28faa5.tar.bz2
docs-26d4f610d11bcb2edca2f201341df18ecd28faa5.zip
still on "example essay store"
Diffstat (limited to 'example-essay-store.rst')
-rw-r--r--example-essay-store.rst14
1 files changed, 7 insertions, 7 deletions
diff --git a/example-essay-store.rst b/example-essay-store.rst
index 5a1539a7..68079a20 100644
--- a/example-essay-store.rst
+++ b/example-essay-store.rst
@@ -66,19 +66,19 @@ by adding the merchant-specific constant `REFUND_DELTA` to the contract's timest
Describing implementation of the above scenario
The essay store, available at https://blog.demo.taler.net, is such that its homepage
-is basically a list to buyable articles and each list item is a reference to an `offering
+is a list of buyable articles and each list item is a reference to an `offering
URL` (see :ref:`offer`). In particular, this offering URL has the following format:
- `/essay_fulfillment.php?article=articleId`
+ `https://blog.demo.taler.net/essay_fulfillment.php?article=articleId`
It is worth noting that in our implementation the `offering` and the `fulfillment` URLs
-differ only respect to the given parameters to the path `/essay_fulfillment.php`. Namely,
-it acts as a fulfillment URL when the user adds the parameters needed to reconstruct the
-contract, which are `tid` (transaction id) and `timestamp` (see :ref:`tsref-type-Contract`,
-and :ref:`ffil`). For the sake of completeness,
+differ only respect to the parameters given to the path `/essay_fulfillment.php`. Namely,
+the offering URL becomes a fulfillment URL whenever the user adds the parameters needed to
+reconstruct the contract, which are `tid` (transaction id) and `timestamp`
+(see :ref:`contract`, and :ref:`ffil`). For the sake of completeness,
- `/essay_fulfillment.php?article=articleId&tid=3489&timestamp=8374738`
+ `https://blog.demo.taler.net/essay_fulfillment.php?article=articleId&tid=3489&timestamp=8374738`
would be a fulfillment URL.