From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: fast list
Date: Mon, 18 Oct 2010 00:02:33 +0200 [thread overview]
Message-ID: <m3mxqcxyti.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m3zkudpffu.fsf@carbon.jhcloos.org>
James Cloos <cloos@jhcloos.com> writes:
> RFC 5819 defines an extension to LIST which returns STATUS replies
> interleaved with the normal LIST replies. Using that should speed
> gnus startup considerably.
>
> Gnus needs to note the LIST-STATUS capability; when it exists gnus
> should send commands akin to:
>
> C: A01 LIST "" % RETURN (STATUS (MESSAGES UNSEEN))
>
> specifying what status info it wants for each group.
>
> RETURN (STATUS (MESSAGES RECENT UIDNEXT UIDVALIDITY UNSEEN))
>
> would be OK here.
That doesn't really help Gnus all that much, since Gnus needs to do a
marks resync, and getting the numbers of each of these won't give Gnus
the data it needs.
If they'd implemented LIST RETURN QRESYNC instead, that would have been
awesome.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-10-17 22:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 5:15 James Cloos
2010-10-17 22:02 ` Lars Magne Ingebrigtsen [this message]
2010-10-17 22:58 ` James Cloos
2010-10-18 19:10 ` Lars Magne Ingebrigtsen
2010-10-18 20:49 ` James Cloos
2010-10-18 21:03 ` Lars Magne Ingebrigtsen
2010-10-18 23:17 ` James Cloos
2010-10-18 23:38 ` Lars Magne Ingebrigtsen
2010-10-19 16:00 ` James Cloos
2010-10-19 16:13 ` Steinar Bang
2010-10-19 18:12 ` Lars Magne Ingebrigtsen
2010-10-19 20:56 ` James Cloos
2010-10-19 18:12 ` Lars Magne Ingebrigtsen
2010-10-19 21:05 ` James Cloos
2010-10-20 0:07 ` Lars Magne Ingebrigtsen
2010-10-20 18:47 ` James Cloos
2010-10-21 15:59 ` Lars Magne Ingebrigtsen
2010-10-21 19:13 ` James Cloos
2010-10-22 14:51 ` Lars Magne Ingebrigtsen
2010-10-19 5:58 ` Steinar Bang
2010-10-19 18:11 ` Lars Magne Ingebrigtsen
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=m3mxqcxyti.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).