aboutsummaryrefslogtreecommitdiff
path: root/doc/handbook/chapters/developer.texi
diff options
context:
space:
mode:
authorSchanzenbach, Martin <mschanzenbach@posteo.de>2019-06-21 22:48:45 +0200
committerSchanzenbach, Martin <mschanzenbach@posteo.de>2019-06-21 22:48:45 +0200
commit96f72f827b3bdc01f9a75ec1913a9e15dcb608ea (patch)
tree4e1abf6192f8f8129dd68fcd63d30394e70f78b5 /doc/handbook/chapters/developer.texi
parent91795c6f87a88ed1c1cd893dd926d823c197b647 (diff)
parentd9e1a8e92cfd95e8f5dba3e5bc000de9b9cf49ac (diff)
downloadgnunet-96f72f827b3bdc01f9a75ec1913a9e15dcb608ea.tar.gz
gnunet-96f72f827b3bdc01f9a75ec1913a9e15dcb608ea.zip
Merge branch 'master' of git+ssh://gnunet.org/gnunet
Diffstat (limited to 'doc/handbook/chapters/developer.texi')
-rw-r--r--doc/handbook/chapters/developer.texi8
1 files changed, 6 insertions, 2 deletions
diff --git a/doc/handbook/chapters/developer.texi b/doc/handbook/chapters/developer.texi
index 3225a6359..b725f4111 100644
--- a/doc/handbook/chapters/developer.texi
+++ b/doc/handbook/chapters/developer.texi
@@ -556,7 +556,7 @@ stacked together to construct complex buildings and it is generally easy
556to swap one block for a different one that has the same shape. GNUnet's 556to swap one block for a different one that has the same shape. GNUnet's
557architecture is based on LEGOs: 557architecture is based on LEGOs:
558 558
559@c @image{images/service_lego_block,5in,,picture of a LEGO block stack - 3 APIs as connectors upon Network Protocol on top of a Service} 559@image{images/service_lego_block,5in,,picture of a LEGO block stack - 3 APIs upon IPC/network protocol provided by a service}
560 560
561This chapter documents the GNUnet LEGO system, also known as GNUnet's 561This chapter documents the GNUnet LEGO system, also known as GNUnet's
562system architecture. 562system architecture.
@@ -573,10 +573,14 @@ Like services, they have holes to be filled by APIs of other services.
573Unlike services, daemons do not implement their own network protocol and 573Unlike services, daemons do not implement their own network protocol and
574they have no API: 574they have no API:
575 575
576@image{images/daemon_lego_block,5in,,A daemon in GNUnet is a component that does not offer an API for others to build upon}
577
576The GNUnet system provides a range of services, daemons and user 578The GNUnet system provides a range of services, daemons and user
577interfaces, which are then combined into a layered GNUnet instance (also 579interfaces, which are then combined into a layered GNUnet instance (also
578known as a peer). 580known as a peer).
579 581
582@image{images/service_stack,5in,,A GNUnet peer consists of many layers of services}
583
580Note that while it is generally possible to swap one service for another 584Note that while it is generally possible to swap one service for another
581compatible service, there is often only one implementation. However, 585compatible service, there is often only one implementation. However,
582during development we often have a "new" version of a service in parallel 586during development we often have a "new" version of a service in parallel
@@ -587,7 +591,7 @@ easily investigated by swapping out individual components. This is
587typically achieved by simply changing the name of the "BINARY" in the 591typically achieved by simply changing the name of the "BINARY" in the
588respective configuration section. 592respective configuration section.
589 593
590Key properties of GNUnet services are that they must be separate 594Key properties of GNUnet services are that they must be separate
591processes and that they must protect themselves by applying tight error 595processes and that they must protect themselves by applying tight error
592checking against the network protocol they implement (thereby achieving a 596checking against the network protocol they implement (thereby achieving a
593certain degree of robustness). 597certain degree of robustness).