added diagrams to Ascension developer handbook

diff --git a/doc/handbook/chapters/developer.texi b/doc/handbook/chapters/developer.texi
index a43bd7b37dd028749908e5ef8471b7c1b2f4c26d..830a345a8232e47d1158c21c578d97ff0135c535 100644 (file)
--- a/doc/handbook/chapters/developer.texi
+++ b/doc/handbook/chapters/developer.texi
@@ -592,7 +592,7 @@ easily investigated by swapping out individual components. This is
 typically achieved by simply changing the name of the "BINARY" in the
 respective configuration section.
 
-Key properties of GNUnet services are that they must be separate        
+Key properties of GNUnet services are that they must be separate
 processes and that they must protect themselves by applying tight error
 checking against the network protocol they implement (thereby achieving a
 certain degree of robustness).
@@ -7958,6 +7958,14 @@ This section discusses the challenges and problems faced when writing the
 Ascension tool. It also takes a look at possible improvements in the
 future.
 
+Consider the following diagram that shows the workflow of Ascension:
+
+@image{images/ascension_ssd,6in,,Ascensions workflow}
+
+Further the interaction between components of GNUnet are shown in the diagram
+below:
+@center @image{images/ascension_interaction,,6in,Ascensions workflow}
+
 @menu
 * Conversions between DNS and GNS::
 * DNS Zone Size::

diff --git a/doc/handbook/images/ascension_interaction.png b/doc/handbook/images/ascension_interaction.png
new file mode 100644 (file)
index 0000000..84e2e9c
Binary files /dev/null and b/doc/handbook/images/ascension_interaction.png differ

diff --git a/doc/handbook/images/ascension_ssd.png b/doc/handbook/images/ascension_ssd.png
new file mode 100644 (file)
index 0000000..3b142ab
Binary files /dev/null and b/doc/handbook/images/ascension_ssd.png differ