[gnunet-scheme] 30/42: doc/service-communication: Document the control loop.

[gnunet]

This is an automated email from the git hooks/post-receive script.

maxime-devos pushed a commit to branch master
in repository gnunet-scheme.

commit b6757584ac1291c4d164e3e2da16a74b461dda7f
Author: Maxime Devos <maximedevos@telenet.be>
AuthorDate: Fri Sep 9 21:18:57 2022 +0200

    doc/service-communication: Document the control loop.
    
    * doc/service-communication (Writing service communication code):
    Add paragraph.
---
 doc/service-communication.tm | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/doc/service-communication.tm b/doc/service-communication.tm
index 5f6cdf9..1c083b5 100644
--- a/doc/service-communication.tm
+++ b/doc/service-communication.tm
@@ -487,6 +487,15 @@
   to the control channel, or wait for the terminal condition to be signalled
   (but not both!).
 
+  The control loop needs various information \V this information is stored in
+  an object of type <scm|\<less\>loop\<gtr\>>, which is simply called a
+  <dfn|loop>. The procedure <scm|make-loop> makes a new loop, <scm|run-loop>
+  enters the loop and <scm|spawn-server-loop> combines making a new loop with
+  entering the loop in the background. In the <em|connect> procedure,
+  <scm|spawn-server-loop> would be called.
+
+  To start a new loop, the procedure <scm|spawn-server-loop> is used
+
   <todo|unify implementation of control loop?>
 
   <todo|TODO: module is not yet complete!>

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.