Re: message registry for Gnus

[Raja R Harinath <harinath@cs.umn.edu>]

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Sat, 01 Feb 2003, harinath@cs.umn.edu wrote:
>> See
>> 
>>   http://article.gmane.org/gmane.emacs.gnus.general/8065
>> 
>> for some of the possible uses for the registry.  I'm sure the actual
>> mechanics suggested there are somewhat bogus.
>
> Wow, you posted that in 1996?  You've been slacking :)

[blush]

But as Lars said then, the set of message-ids covered were somewhat
disjoint.  If we now have a registry of all mail message-ids, then
it's more appropriate now.

> :seen is not needed as you state, is it?  We only need to store the
> actual article number and full group name associated with the message
> ID in a property that's a list each time we see the message ID
> spooled, copied, or moved.  If there are more than one entries in the
> list, the article is duplicated somewhere.  This is sufficient to find
> any article's copies by message ID.

Yep.  However, the idea was for an in-memory data structure only.
So, I wanted a doubly-linked-list to get at all the seen msgids to
save as ~/News/suppression.  Anyway, I didn't say the design was good :-)

> :refs-to and :has-refs-from seem to be better off in a separate table
> (if articles are nodes in a graph and references are edges - for a
> generic graph it's easier to store the edges in a separate table if I
> remember my database design)

This is the 'adjacency list' data structure -- good in-memory, and not
too shabby for saving on-disk, esp. in a custom registry.

- Hari
-- 
Raja R Harinath ------------------------------ harinath@cs.umn.edu