From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: [PATCH] Use IMAP MOVE extension if available
Date: Sun, 02 Aug 2015 21:08:54 -0400 [thread overview]
Message-ID: <87si81b2l5.fsf@uwo.ca> (raw)
In-Reply-To: <87vbcx460o.fsf@vostro.rath.org>
Nikolaus Rath <Nikolaus@rath.org> writes:
> I don't understand this worry about one additional back and forth during
> *login*. For me, starting Gnus takes about 2 seconds, and issuing the
> CAPABILITY command takes about 160 ms. Is it really worth optimizing
> this?
I believe that Gnus has to re-login now and then, e.g. when connections
are idle for too long. Logging in to my remote IMAP server currently
takes a bit under 1s, so the above could presumably add 10 to 20% to the
time taken to open a group. If it's possible to avoid the round-trip
when it isn't needed, it seems like it would be a good idea. (I haven't
followed the details of this discussion, so I don't know how hard it
would be to implement this.)
Dan
next prev parent reply other threads:[~2015-08-03 1:08 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 [this message]
2015-08-03 8:17 ` Steinar Bang
2015-08-03 17:18 ` Nikolaus Rath
2015-08-04 3:17 ` Eric Abrahamsen
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=87si81b2l5.fsf@uwo.ca \
--to=jdc@uwo.ca \
--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).