Gnus development mailing list
 help / color / mirror / Atom feed
From: Julien Danjou <julien@danjou.info>
To: ding@gnus.org
Subject: Re: 'g' transfers a lot of data
Date: Fri, 08 Oct 2010 11:31:18 +0200	[thread overview]
Message-ID: <87d3rl115l.fsf@keller.adm.naquadah.org> (raw)
In-Reply-To: <m3ocb594f7.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 07 Oct 2010 21:41:16 +0200")

[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]

On Thu, Oct 07 2010, Lars Magne Ingebrigtsen wrote:

>> Maybe 100 is not enough actually?
>> How others MUA plays with that?
>
> The only way to get the flags data (without QRESYNC) is to say "UID
> FETCH FLAGS 1:*".  If you have 200K messages in that group, it'll take a
> while.
>
> When all IMAP servers get QRESYNC support this will be a moot issue, but
> at present you have to trade off accuracy for speed in this area.  I
> think other MUAs do opportunistic FLAGS sync in the background.

I took a look a mutt, and from what I understand it does 2 things:
- to know if there's new mail, it uses the STATUS command.

  . STATUS INBOX (UIDNEXT UIDVALIDITY UNSEEN RECENT MESSAGES)
  * STATUS "INBOX" (MESSAGES 11790 RECENT 0 UIDNEXT 26293 UIDVALIDITY 1247083159 UNSEEN 1)

  That seems enough to use for 'g'.

- Store the UIDVALIDITY value permanently for each mailbox, and whenever
  it changes refetch all information for all mails in that mailbox.

That sounds safer than the current behaviour, and probably not
complicated to implement. WDYT Lars? :)

-- 
Julien Danjou
// ᐰ <julien@danjou.info>   http://julien.danjou.info

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2010-10-08  9:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05 11:30 Julien Danjou
2010-10-05 16:55 ` Lars Magne Ingebrigtsen
2010-10-05 18:55   ` Julien Danjou
2010-10-05 20:10     ` Lars Magne Ingebrigtsen
2010-10-06  9:22       ` Julien Danjou
2010-10-06 10:33         ` Steinar Bang
2010-10-07 19:41         ` Lars Magne Ingebrigtsen
2010-10-08  9:31           ` Julien Danjou [this message]

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=87d3rl115l.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).