Re: fast list

[James Cloos <cloos@jhcloos.com>]

>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

JC> RETURN (STATUS (MESSAGES RECENT UIDNEXT UIDVALIDITY UNSEEN))

LMI> That doesn't really help Gnus all that much, since Gnus needs to do a
LMI> marks resync, and getting the numbers of each of these won't give Gnus
LMI> the data it needs.

LMI> If they'd implemented LIST RETURN QRESYNC instead, that would have been
LMI> awesome.

What, exactly, does gnus need for each group?

DBmail doesn't store arbitrary marks, so I don't need mark syncing for
gnus' internal marks.

I don't have a recent packet trace, but doesn't it just do a LIST
followed by either EXAMINE or STATUS?  LIST-STATUS does that pair
of ops in a single op.  And that has to speed startup.

I expect that:

  LIST "" "%" RETURN (STATUS (MESSAGES RECENT UIDNEXT UIDVALIDITY UNSEEN))

will take less than one second whereas running STATUS or EXAMINE on
every group returned by LIST takes about fifteen minutes.

I can ensure that my patches to dbmail support more than just messages,
recent, uidnext, uidvalidity and unseen if that helps.

BTW, based on:

  http://permalink.gmane.org/gmane.mail.imap.dovecot/51621

it looks like dovecot 2.0 also supports LIST-STATUS.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6