From 7d7ccbcdbdc45e72b30cb180eaf892dc782c408a Mon Sep 17 00:00:00 2001 From: Christian Grothoff Date: Wed, 14 Mar 2018 05:22:48 +0100 Subject: [PATCH] Hi Christian, Thank you! Very cool to see the example working. Funny, I implemented MHD_get_timeout in the main loop in my project but in all my tests it always returned MHD_NO, so I assumed it was not applicable to my use case and didn't include it in the example I wrote. But I didn't make the connection that it *also* had to be called after MHD_resume_connection until your response here. Would you consider the attached patch? It adds one line to the docs that I'm quite sure would have pointed me in the right direction had it been there before. Thanks! Bob --- src/include/microhttpd.h | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/include/microhttpd.h b/src/include/microhttpd.h index b4e436c2..cff084ed 100644 --- a/src/include/microhttpd.h +++ b/src/include/microhttpd.h @@ -2562,10 +2562,10 @@ MHD_suspend_connection (struct MHD_Connection *connection); * result in undefined behavior. * * If you are using this function in ``external'' select mode, you must - * make sure to run #MHD_run() afterwards (before again calling - * #MHD_get_fdset(), as otherwise the change may not be reflected in - * the set returned by #MHD_get_fdset() and you may end up with a - * connection that is stuck until the next network activity. + * make sure to run #MHD_run() and #MHD_get_timeout() afterwards (before + * again calling #MHD_get_fdset()), as otherwise the change may not be + * reflected in the set returned by #MHD_get_fdset() and you may end up + * with a connection that is stuck until the next network activity. * * @param connection the connection to resume */