From: Ted Zlatanov <tzz@lifelogs.com>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: closing all inactive server connections
Date: Thu, 16 Aug 2007 10:56:24 -0500 [thread overview]
Message-ID: <m2zm0rjwwn.fsf@lifelogs.com> (raw)
In-Reply-To: <m28x8blcll.fsf@lifelogs.com> (Ted Zlatanov's message of "Thu, 16 Aug 2007 10:32:06 -0500")
On Thu, 16 Aug 2007 10:32:06 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote:
TZ> On Wed, 15 Aug 2007 13:28:44 +0200 Simon Josefsson <simon@josefsson.org> wrote:
SJ> Ted Zlatanov <tzz@lifelogs.com> writes:
>>> Maybe it should be generalized, however, to an IMAP timeout per (server,
>>> group name, command) combination (as a regex or a function), so you can
>>> assign "LOGOUT" a longer timeout with a slower server. This could also
>>> be a server tuning parameter for nnimap instead of an imap.el parameter.
SJ> Having the timeout be restricted to just LOGOUT seems to make more sense
SJ> to me. If the server doesn't respond to a LOGOUT within a short period
SJ> of time, one might as well disconnect.
TZ> That's fine. So it should be imap-logout-timeouts, an alist of
TZ> (server-regex seconds) cells. Agreed?
Here's the defcustom I was thinking of:
(defcustom imap-logout-timeout nil
"Close server immediately if it can't logout in this number of seconds.
If it is nil, never close server until logout completes."
:version "23.0" ;; No Gnus.
:group 'imap
:type '(choice (const :tag "No timeout" nil)
(number :value 1.0)
(repeat :tag "Set individual timeouts per server"
(list :tag "Server/timeout combination"
(regexp :tag "Server name regular expression")
(choice
(number :value 1.0 :tag "Logout timeout for this server")
(const :tag "No timeout" nil))))))
Then imap-logout has to be modified too, but I want to make sure this is OK.
Ted
next prev parent reply other threads:[~2007-08-16 15:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 15:59 Ted Zlatanov
2007-07-10 19:54 ` Ted Zlatanov
2007-07-19 13:46 ` Ted Zlatanov
2007-07-27 17:06 ` Ted Zlatanov
2007-07-28 0:18 ` Ted Zlatanov
2007-07-30 6:22 ` Katsumi Yamaoka
2007-07-30 15:39 ` Ted Zlatanov
2007-07-31 2:57 ` Katsumi Yamaoka
2007-07-31 3:08 ` Katsumi Yamaoka
2007-07-31 3:19 ` Ted Zlatanov
2007-07-31 8:52 ` Katsumi Yamaoka
2007-08-02 19:51 ` Ted Zlatanov
2007-08-15 11:28 ` Simon Josefsson
2007-08-16 7:18 ` Katsumi Yamaoka
2007-08-16 7:25 ` Katsumi Yamaoka
2007-08-16 9:49 ` Simon Josefsson
2007-08-16 15:35 ` Ted Zlatanov
2007-08-16 15:32 ` Ted Zlatanov
2007-08-16 15:56 ` Ted Zlatanov [this message]
2007-08-16 23:19 ` Katsumi Yamaoka
2007-08-16 23:25 ` Ted Zlatanov
2007-08-16 23:47 ` Katsumi Yamaoka
2007-08-17 11:09 ` Katsumi Yamaoka
2007-09-10 14:52 ` Ted Zlatanov
2007-08-15 18:28 ` Reiner Steib
2007-07-31 3:16 ` Ted Zlatanov
2007-07-31 3:19 ` Katsumi Yamaoka
2007-07-31 2:58 ` untabify Lisp sources (was Re: closing all inactive server connections) Katsumi Yamaoka
2007-07-31 22:05 ` untabify Lisp sources Reiner Steib
2007-08-01 2:44 ` Ted Zlatanov
2007-07-31 22:57 ` Miles Bader
2007-08-01 2:46 ` Ted Zlatanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2zm0rjwwn.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=yamaoka@jpl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).