From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Backend writing
Date: Sat, 04 Aug 2001 13:46:40 +0200 [thread overview]
Message-ID: <vaf3d78hwtb.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <iluu1zod8el.fsf@barbar.josefsson.org> (Simon Josefsson's message of "Sat, 04 Aug 2001 01:35:14 +0200")
Simon Josefsson <jas@extundo.com> writes:
> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>
>> But haven't you just changed nnimap to ignore article renumberings? I
>> suppose you wouldn't do that unless it's safe?
>
> I don't know if it's safe, that's what Oort is for. <g>
He, he.
> Basicly, nnimap makes sure the old NOV cache isn't used when a
> uidvalidity has changed. Nnimap also updates all Gnus marks when
> entering a group so they should be OK. The only thing left is the
> active range, and that's updated by Gnus when you `g', `M-g' or
> somesuch. Possibly a uidvalidity change breaks the cache or the agent
> if article numbers are actually re-used. But in several cases IMAP
> servers update UIDVALIDITY but still does not re-use article numbers,
> so in those cases it's OK to ignore the error.
My goodness. I didn't think of the agent and the cache. Hmpf.
kai
--
~/.signature: No such file or directory
prev parent reply other threads:[~2001-08-04 11:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-03 18:04 Sean Rima
2001-08-03 19:24 ` Kai Großjohann
2001-08-03 19:39 ` Paul Jarc
2001-08-03 20:57 ` Kai Großjohann
2001-08-03 21:36 ` Paul Jarc
2001-08-03 22:16 ` Kai Großjohann
2001-08-03 21:44 ` Simon Josefsson
2001-08-03 22:07 ` Kai Großjohann
2001-08-03 23:35 ` Simon Josefsson
2001-08-03 23:46 ` Paul Jarc
2001-08-04 0:11 ` Simon Josefsson
2001-08-04 0:20 ` Paul Jarc
2001-08-04 0:41 ` Simon Josefsson
2001-08-04 0:57 ` Paul Jarc
2001-08-04 12:36 ` Simon Josefsson
2001-08-05 8:27 ` Paul Jarc
2001-08-03 23:57 ` Paul Jarc
2001-08-04 0:12 ` Simon Josefsson
2001-08-04 0:21 ` Paul Jarc
2001-08-04 11:46 ` Kai Großjohann [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=vaf3d78hwtb.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).