Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: nnima-split-with-parent
Date: Fri, 06 Dec 2002 15:24:36 -0500	[thread overview]
Message-ID: <4n7kemaoaj.fsf@brainy.bwh.harvard.edu> (raw)

I want nnimap-split-with-parent! :) 

I was looking at the nnmail-split-with-parent code, and I see that the
nnmail cache is used for duplicate detection *and* for splitting with
the parent.  So it's not easy to abstract the nnmail cache as it is to
arbitrary newsgroup names, we might get erroneous warnings about
duplicates.  I think the format for the "new" article-ID cache should
be

backend-name\tarticle-ID\tgroup-name

We can keep the current nnmail cache as well, but this format can
replace the old cache format with very little work.  Maybe we can copy
and fix up the new-cache from the old nnmail-cache if we're upgrading,
and otherwise always use the new-cache file?

We should separate the functionality into gnus-article-cache.el if
it's going to be generalized (or whatever the file is called).

Functions affected (new names are not necessarily final):

nnmail-cache-insert: needs to be generalized to
gnus-article-cache-insert, maybe figuring out the backend name instead
of having it passed in for minimum code changes?

nnmail-cache-fetch-group: needs to be generalized to
gnus-article-cache-fetch-group, and the logic altered a little to
allow for the backend name at beggining of line.  Like the insert
function, maybe it should figure out the current backend name instead
of having it passed in for minimum code changes?

nnmail-cache-id-exists-p: generalize to
gnus-article-cache-id-exists-p, unchanged otherwise

the other nnmail-cache-* functions should be easily migrated to
gnus-article-cache-*

I hope someone is interested in doing this or at least giving me some
feedback...

Ted



             reply	other threads:[~2002-12-06 20:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06 20:24 Ted Zlatanov [this message]
2002-12-07 14:59 ` nnima-split-with-parent Kai Großjohann
2002-12-07 18:20   ` nnima-split-with-parent Ted Zlatanov
2002-12-07 20:22     ` nnima-split-with-parent Kai Großjohann
     [not found] ` <m2k7imroo1.fsf@tnuctip.rychter.com>
2002-12-07 13:54   ` nnimap-split-with-parent Ted Zlatanov
2002-12-07 15:01   ` nnima-split-with-parent Kai Großjohann
2002-12-07 15:14     ` nnima-split-with-parent Ted Zlatanov
2002-12-07 15:28       ` nnima-split-with-parent Kai Großjohann
2002-12-07 18:20         ` nnima-split-with-parent Ted Zlatanov
2002-12-07 20:25           ` nnima-split-with-parent Kai Großjohann
2002-12-09 15:54             ` nnima-split-with-parent Ted Zlatanov
2002-12-09 16:21               ` nnima-split-with-parent Kai Großjohann
     [not found]     ` <m27kelycce.fsf@tnuctip.rychter.com>
2002-12-07 20:23       ` nnima-split-with-parent Kai Großjohann

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=4n7kemaoaj.fsf@brainy.bwh.harvard.edu \
    --to=tzz@lifelogs.com \
    /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).