gnunet

Main GNUnet Logic
Log | Files | Refs | Submodules | README | LICENSE

commit 6df975dccc4f2a8929473374e68518a847f112a2
parent 988ac7f121b646cba3ca44567f54b1315398505d
Author: rexxnor <rexxnor+gnunet@brief.li>
Date:   Sun, 23 Jun 2019 10:41:42 +0200

added diagrams to Ascension developer handbook

Diffstat:
Mdoc/handbook/chapters/developer.texi | 10+++++++++-
Adoc/handbook/images/ascension_interaction.png | 0
Adoc/handbook/images/ascension_ssd.png | 0
3 files changed, 9 insertions(+), 1 deletion(-)

diff --git 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 Binary files differ. diff --git a/doc/handbook/images/ascension_ssd.png b/doc/handbook/images/ascension_ssd.png Binary files differ.