From 191521751beef68b2fcfe0cc6ca9a987409f7fce Mon Sep 17 00:00:00 2001
From: Matteo Cypriani <matteo.cypriani@uqat.ca>
Date: Thu, 3 Oct 2013 09:49:34 -0400
Subject: [PATCH] [doc] architecture: add process diagram

---
 doc/owlps-architecture.t2t | 23 ++++++++++++++++++++++-
 1 file changed, 22 insertions(+), 1 deletion(-)

diff --git a/doc/owlps-architecture.t2t b/doc/owlps-architecture.t2t
index d53471c..ad7c5f3 100644
--- a/doc/owlps-architecture.t2t
+++ b/doc/owlps-architecture.t2t
@@ -62,7 +62,28 @@ Each step of this protocol corresponds to a different module:
   The positioning server, or computation server, takes as an input the
   data from the aggregation server, and outputs the computed positions,
   thanks to the //OwlPS Positioner// module, described in detail in
-  owlps-positionerd.t2t.
+  owlps-positionerd.t2t. These results can be sent to the mobile
+  terminal or treated otherwise, for instance by a program such as OwlPS
+  UDP-to-HTTP (cf. owlps-udp-to-http.t2t).
+
+
+The figure below summarises this process:
+
+```
+      +--------------+     positioning request      +----------------+
+      | OwlPS Client | ---------------------------> | OwlPS Listener |
+      +--------------+                              +----------------+
+              ^                                             |
+              |                                             |
+              |                                             | captured
+     computed |                                             | request
+     position |                                             |
+              |                                             |
+              |                                             V
+    +------------------+     aggregated request    +------------------+
+    | OwlPS Positioner | <------------------------ | OwlPS Aggregator |
+    +------------------+                           +------------------+
+```