aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMaxime Devos <maximedevos@telenet.be>2022-09-09 21:18:57 +0200
committerMaxime Devos <maximedevos@telenet.be>2022-09-09 21:18:57 +0200
commitb6757584ac1291c4d164e3e2da16a74b461dda7f (patch)
treeb309c549d18530655c2819bd1d514e6f57cd25ca
parente5ccd5ad1ff65dd43a89b3a1132c06397e643881 (diff)
downloadgnunet-scheme-b6757584ac1291c4d164e3e2da16a74b461dda7f.tar.gz
gnunet-scheme-b6757584ac1291c4d164e3e2da16a74b461dda7f.zip
doc/service-communication: Document the control loop.
* doc/service-communication (Writing service communication code): Add paragraph.
-rw-r--r--doc/service-communication.tm9
1 files changed, 9 insertions, 0 deletions
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 @@
487 to the control channel, or wait for the terminal condition to be signalled 487 to the control channel, or wait for the terminal condition to be signalled
488 (but not both!). 488 (but not both!).
489 489
490 The control loop needs various information \V this information is stored in
491 an object of type <scm|\<less\>loop\<gtr\>>, which is simply called a
492 <dfn|loop>. The procedure <scm|make-loop> makes a new loop, <scm|run-loop>
493 enters the loop and <scm|spawn-server-loop> combines making a new loop with
494 entering the loop in the background. In the <em|connect> procedure,
495 <scm|spawn-server-loop> would be called.
496
497 To start a new loop, the procedure <scm|spawn-server-loop> is used
498
490 <todo|unify implementation of control loop?> 499 <todo|unify implementation of control loop?>
491 500
492 <todo|TODO: module is not yet complete!> 501 <todo|TODO: module is not yet complete!>