gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[gnunet-scheme] 134/324: mq: Clarify how a message handlers are chosen.


From: gnunet
Subject: [gnunet-scheme] 134/324: mq: Clarify how a message handlers are chosen.
Date: Tue, 21 Sep 2021 13:22:54 +0200

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 67cec521d00ffb7bf48eef20a85545de238f64f1
Author: Maxime Devos <maximedevos@telenet.be>
AuthorDate: Tue Jun 15 15:25:46 2021 +0200

    mq: Clarify how a message handlers are chosen.
    
    * gnu/gnunet/mq.scm
      (make-message-queue): Clarify in the docstring that the index of the
      message handler corresponds to the message type.
---
 gnu/gnunet/mq.scm | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/gnu/gnunet/mq.scm b/gnu/gnunet/mq.scm
index ba63db4..c77db34 100644
--- a/gnu/gnunet/mq.scm
+++ b/gnu/gnunet/mq.scm
@@ -87,7 +87,10 @@
           "Make a message queue with message handlers @var{handlers}.
 
 The message handlers are expected to handle bytevector slices
-that start with a @code{/:message-header}.
+that start with a @code{/:message-header}. The index of the message
+handler is the ‘message type’.  Note that, unlike in the C implementation,
+messages are not serialised.  As such, some synchronisation or punting
+messages onto a separate thread may be necessary.
 
 XXX and error handler @var{error-handler}
 

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]