From: Julien Danjou <julien@danjou.info>
To: ding@gnus.org
Subject: Re: Returning to ticks on read-only imap servers
Date: Fri, 08 Oct 2010 20:22:38 +0200 [thread overview]
Message-ID: <87zkuozgr5.fsf@keller.adm.naquadah.org> (raw)
In-Reply-To: <m31v80liw5.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Fri, 08 Oct 2010 19:00:10 +0200")
[-- Attachment #1: Type: text/plain, Size: 1400 bytes --]
On Fri, Oct 08 2010, Lars Magne Ingebrigtsen wrote:
> Yeah. I think I have a clear idea how to proceed here now. For groups
> it knows already, it'll output either EXAMINE+FETCH (or EXAMINE QRESYNC)
> for the servers that support that. For groups it doesn't know, it'll
> output a SELECT+FETCH 1:*. That SELECT will tell nnimap whether it
> supports flags or not, and nnimap can then stash that info.
>
> In the same sweep, it'll examine the EXAMINE results for mismatches in
> UIDVALIDITY, and do an extra SELECT+FETCH 1:* for those groups.
>
> So for normal `g' work, it'll be no slower than today (and much, much
> faster for servers with QRESYNC). Only the appearance of new groups, or
> UIDVALIDITY mismatches, will trigger more chatter between Gnus and the
> IMAP server.
>
> I'll work on implementing this this weekend. Once it's implemented, the
> very first time you use Gnus after the push, Gnus will issue a
> SELECT+FETCH 1:* for all your groups to get a complete data set again.
That overlaps was I was saying in an earlier mail today, using
UIDVALIDITY to resync everything rather than fetch the 100 last mails.
The only question left is, are you forced to to a FETCH 1:*, isn't a
STATUS enough? That would be very faster. You'd do the FETCH on group
entering.
My 2¢,
--
Julien Danjou
// ᐰ <julien@danjou.info> http://julien.danjou.info
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-10-08 18:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 19:16 Michael Welsh Duggan
2010-10-05 20:25 ` Steinar Bang
2010-10-05 21:01 ` Michael Welsh Duggan
2010-10-07 18:59 ` Lars Magne Ingebrigtsen
2010-10-07 21:37 ` Michael Welsh Duggan
2010-10-07 22:40 ` Lars Magne Ingebrigtsen
2010-10-08 15:07 ` James Cloos
2010-10-08 17:00 ` Lars Magne Ingebrigtsen
2010-10-08 18:22 ` Julien Danjou [this message]
2010-10-08 18:26 ` Lars Magne Ingebrigtsen
2010-10-08 18:28 ` Julien Danjou
2010-10-08 18:49 ` Lars Magne Ingebrigtsen
2010-10-08 19:34 ` Julien Danjou
2010-10-08 21:32 ` Dan Christensen
2010-10-09 6:57 ` Julien Danjou
2010-10-09 8:10 ` Michael Welsh Duggan
2010-10-09 8:26 ` Julien Danjou
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=87zkuozgr5.fsf@keller.adm.naquadah.org \
--to=julien@danjou.info \
--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).