From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Should Message-Ids become first-class Gnus objects?
Date: 27 Sep 1996 19:15:12 +0200 [thread overview]
Message-ID: <w8su3sjg9r3.fsf@ylfing.ifi.uio.no> (raw)
In-Reply-To: Raja R Harinath's message of 26 Sep 1996 18:51:15 -0500
Raja R Harinath <harinath@cs.umn.edu> writes:
> There are many lists of Message-Ids that duplicate information. For
> eg., `gnus-dup' maintains a list and an obarray of message-ids already
> seen. `gnus-gl' maintains a list of message-ids rated. All these are
> separate obarrays, and duplicate the message-id string.
>
> I wonder if using a single message-id hashtb with the other facilities
> being implemented as property get/sets will be a better alternative.
> This would require a major rearchitecting of Gnus.
Well, all the different functions use a different subset of
Message-IDs, and the Message-IDs live for a shorter or longer time. I
think trying to make One Unified Message-ID thingie could be quite
difficult.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
prev parent reply other threads:[~1996-09-27 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-09-26 23:51 Raja R Harinath
1996-09-27 17:15 ` Lars Magne Ingebrigtsen [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=w8su3sjg9r3.fsf@ylfing.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).