From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: nnimap question
Date: Wed, 16 Jan 2002 15:36:00 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0201161530120.27155-100000@slipsten.extundo.com> (raw)
In-Reply-To: <ey1ygqjsyu.fsf@vsu.ru>
On Wed, 16 Jan 2002, Vladimir Volovich wrote:
> Hi!
>
> when i run gnus-group-get-new-news (g) from the *Group* buffer,
> nnimap spemds a lot of time checking mailboxes: i see
> nnimap: Checking mailbox <mailbox_name>
> in the minibuffer for each of my nnimap mailbox,
> even when there are no new messages.
>
> if it possible to avoid checking nnimap mailboxes for
> gnus-group-get-new-news (or do it only on gnus startup)?
It would be possible, but then nnimap wouldn't notice when you get new
mail in those groups. Some people seems to only receive mail in one
mailbox, and in this case it could be good to make this optimisation. But
when I started implementing it, I remember client-side splitting, which
would break this... maybe the client-side splitting in nnimap can update
it's internal state of which groups have new mail though.
I have also thought about doing this asynchronously in the background, so
that `g' returns immediately, but with possible old data.
Using the STATUS command instead of entering the group could be possible
as well. It could record the UIDNEXT value and only enter the group (to
get highest/lowest article number) if it has changed. Then it could cache
highest/lowest article number for groups. This would work and have no bad
side effects, I think.
There is plenty of room for making things faster, at least...
next prev parent reply other threads:[~2002-01-16 14:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 14:00 Vladimir Volovich
2002-01-16 14:36 ` Simon Josefsson [this message]
2002-01-16 14:58 ` Vladimir Volovich
2002-01-16 15:56 ` David S. Goldberg
2002-01-21 20:44 ` Steinar Bang
-- strict thread matches above, loose matches on Subject: below --
2001-09-26 0:00 Sailesh Krishnamurthy
2001-09-26 7:29 ` Simon Josefsson
2001-09-26 9:29 ` Sailesh Krishnamurthy
2001-09-26 10:53 ` Simon Josefsson
2001-09-26 19:46 ` Sailesh Krishnamurthy
2001-09-26 20:16 ` Simon Josefsson
2001-09-27 0:54 ` Sailesh Krishnamurthy
2001-09-28 4:06 ` Sailesh Krishnamurthy
2001-09-28 12:53 ` Kai Großjohann
2001-09-28 22:21 ` Sailesh Krishnamurthy
2001-09-29 1:15 ` Kai Großjohann
2001-09-30 4:19 ` Amos Gouaux
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=Pine.LNX.4.44.0201161530120.27155-100000@slipsten.extundo.com \
--to=jas@extundo.com \
--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).