[gnunet-scheme] 209/324: doc: Resolve the TODO about broken pipes.

[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 2bc7c2c6adca987a45a9b737be7cd0c621adaef1
Author: Maxime Devos <maximedevos@telenet.be>
AuthorDate: Tue Aug 31 16:15:16 2021 +0200

    doc: Resolve the TODO about broken pipes.
    
    Most potential problems seem to be addressed.
    
    * doc/scheme-gnunet.tm (input:regular-end-of-file): Explain what
      happens if a port becomes half-duplex.
---
 doc/scheme-gnunet.tm | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/doc/scheme-gnunet.tm b/doc/scheme-gnunet.tm
index 49ad672..9fef02e 100644
--- a/doc/scheme-gnunet.tm
+++ b/doc/scheme-gnunet.tm
@@ -327,10 +327,16 @@
 
   <\explain>
     <scm|input:regular-end-of-file>
-  </explain|The connection has been closed by the
-  server.<space|1em><todo|technically, this only means the write end has been
-  closed from the servers' POV.<space|1em>The read part might still be open
-  \V or is that only for pipes? \V TODO>>
+  <|explain>
+    The connection has been closed by the server.
+
+    For people wondering about what happens if a connection becomes
+    half-duplex: GNUnet does not have a notion of half-duplex message
+    streams.<space|1em>If it is detected the underlying stream became
+    half-duplex anyways, it will be treated as closed by scheme-GNUnet,
+    resulting in this error.<space|1em>However, note that currently broken
+    pipes cannot be reliably detected.
+  </explain>
 
   <\explain>
     <scm|input:premature-end-of-file>

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