From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: [PATCH] Use IMAP MOVE extension if available
Date: Tue, 04 Aug 2015 11:17:49 +0800 [thread overview]
Message-ID: <87k2tbyc6a.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87io8wz3we.fsf@thinkpad.rath.org>
Nikolaus Rath <Nikolaus@rath.org> writes:
> On Aug 03 2015, Steinar Bang <sb@dod.no> wrote:
>>>>>>> Dan Christensen <jdc@uwo.ca>:
>>
>>> I believe that Gnus has to re-login now and then, e.g. when connections
>>> are idle for too long.
>>
>> Ok, that may be a case for optimization: the CAPABILITIES may change
>> before and after login, but it is not very likely that they will change
>> for the rest of the session.
>>
>> Ie. issue CAPABILITIES only after the initial login.
>
> Preserving capabilities from one connection to the next would require
> some major coding effort. In that case we're still better of trying very
> hard to extract the capabilities from the LOGIN response.
I'd say we ought to leave it the way it is now, until we've got a better
parser for command responses.
E
next prev parent reply other threads:[~2015-08-04 3:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 0:29 Nikolaus Rath
2015-07-16 9:00 ` Eric Abrahamsen
2015-07-20 9:53 ` Eric Abrahamsen
2015-07-20 16:18 ` Nikolaus Rath
2015-07-27 4:36 ` Eric Abrahamsen
2015-07-27 16:10 ` Nikolaus Rath
2015-08-02 5:56 ` Eric Abrahamsen
2015-08-02 23:36 ` Nikolaus Rath
2015-08-03 0:40 ` Eric Abrahamsen
2015-08-03 1:08 ` Dan Christensen
2015-08-03 8:17 ` Steinar Bang
2015-08-03 17:18 ` Nikolaus Rath
2015-08-04 3:17 ` Eric Abrahamsen [this message]
2015-08-04 17:28 ` Nikolaus Rath
2015-08-05 1:53 ` Eric Abrahamsen
-- strict thread matches above, loose matches on Subject: below --
2015-05-25 19:59 Nikolaus Rath
2015-07-07 2:59 ` Eric Abrahamsen
2015-07-07 3:05 ` Eric Abrahamsen
2015-07-09 2:13 ` Nikolaus Rath
2015-07-09 2:18 ` Eric Abrahamsen
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=87k2tbyc6a.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.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).