From 1d7b336f7c65ab138ba1bae46a4e9c4861c3e12d Mon Sep 17 00:00:00 2001 From: Eduardo Chappa Date: Thu, 6 Feb 2020 15:41:43 -0700 Subject: * Add a help text to the option close-connection-timeout. Reported by Aditya Mahajan. --- pith/conf.c | 2 ++ pith/pine.hlp | 53 ++++++++++++++++++++++++++++++++++++++++++++++++++++- 2 files changed, 54 insertions(+), 1 deletion(-) diff --git a/pith/conf.c b/pith/conf.c index f6fe486..c39a19e 100644 --- a/pith/conf.c +++ b/pith/conf.c @@ -7857,6 +7857,8 @@ config_help(int var, int feature) return(h_config_tcp_writewarn_timeo); case V_TCPQUERYTIMEO : return(h_config_tcp_query_timeo); + case V_QUITQUERYTIMEO : + return(h_config_quit_query_timeo); case V_RSHOPENTIMEO : return(h_config_rsh_open_timeo); case V_SSHOPENTIMEO : diff --git a/pith/pine.hlp b/pith/pine.hlp index dd4ca9a..5246505 100644 --- a/pith/pine.hlp +++ b/pith/pine.hlp @@ -140,7 +140,7 @@ with help text for the config screen and the composer that didn't have any reasonable place to be called from. Dummy change to get revision in pine.hlp ============= h_revision ================= -Alpine Commit 403 2020-02-06 07:31:37 +Alpine Commit 404 2020-02-06 15:41:28 ============= h_news ================= @@ -4673,6 +4673,7 @@ There are also additional details on

OPTION: @@ -25361,6 +25362,56 @@ has a minimum of 5 seconds, and a maximum of 1000 seconds. <End of help on this topic> +====== h_config_quit_query_timeo ===== + + +OPTION:  + + +

OPTION:

+ +The original purpose of this option was to close a connection after this +much time has elapsed without response from the server. The problem this +generates is that a server might not reply on time due to a slow operation +(for example, sorting a large folder, or filtering messages, etc.) In those +situations it is desirable to wait for the server, even when this takes +a long time. + +

+In order to have a good compromise so that a user can distinguish between +when a connection is closed, therefore +we do not need to wait for it, and the operation that the user is waiting +for takes a long time, this option only applies to the +"NOOP" IMAP command. So, if a NOOP command has been issued, +and the connection does not return after the number of seconds configured +here, which must be at least the amount configured in the option +, +then Alpine will close the connection. + +

+Closing connections that have connectivity problems is a good idea. In an ideal +world, one would like all connections to be fast and reliable, so the amount +of time and effort put into parsing a folder to report its state when it is +opened is not wasted, so keeping connections alive is good, but the problem +with this is that waiting for a user to reply to a "keep connection +alive?" question can take a long time, and that might affect other +connections that could be closed because Alpine is not pinging them while it +is waiting for a reply from a user for a different connection. Therefore +setting this value helps to keep other connections alive, in case +you have several incoming folders in other servers. + +

+The default value for this option is 0, which means that no connections will +be closed automatically, so if you want connections to be closed automatically +you must set this option to a positive number bigger or equal than the +value of the option . +

Finding more information and requesting help +

+<End of help on this topic> + + ====== h_config_incoming_folders ===== -- cgit v1.2.3-54-g00ecf