From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Why article numbers?
Date: Sat, 22 Feb 2003 23:33:32 +0100 [thread overview]
Message-ID: <ilur8a07xoj.fsf@latte.josefsson.org> (raw)
In-Reply-To: <84el60hvg9.fsf@lucy.is.informatik.uni-duisburg.de> (kai.grossjohann@uni-duisburg.de's message of "Sat, 22 Feb 2003 22:11:34 +0100")
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>> "A lot of work" is an understatement, but what would the advantages
>> be? (Other than making hard disk and ram manufacturers happy, that
>> is.)
>
> If Gnus stored marks for message ids instead of article numbers:
>
> * you could move from one news server to another without losing your
> marks, and without gnus-move-to-another-server, or what is it
> called;
>
> * nnimap could store marks that survive uidvalidity changes;
>
> * you could mark articles that were retrieved via `^';
>
> * the cache would survive server-side renumbering, as would the agent.
How would you handle two messages with the same message-id? Or no
message-id (think drafts)? Since it is possible to create that
scenario, Gnus should IMHO handle it. I think an abstract data type
separated from the message itself is more flexible. I see two
problems with the use of integers today: handling sets of integers can
be slow, and the integer limit in emacs is too small.
Regarding the nnimap issue, a better solution would IMHO be to fix it
to do proper re-syncing on UIDVALIDITY changes, which it probably
would have to do even if message-id's are used to index articles since
IMAP uses integers to retrieve articles anyway.
next prev parent reply other threads:[~2003-02-22 22:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 21:55 Kai Großjohann
2003-02-08 20:38 ` Lars Magne Ingebrigtsen
2003-02-08 23:44 ` Paul Jarc
2003-02-08 23:49 ` Lars Magne Ingebrigtsen
2003-02-09 14:59 ` Kai Großjohann
2003-02-10 18:40 ` Paul Jarc
2003-02-22 20:24 ` Lars Magne Ingebrigtsen
2003-02-22 21:11 ` Kai Großjohann
2003-02-22 21:24 ` Lars Magne Ingebrigtsen
2003-02-22 21:37 ` Kai Großjohann
2003-02-22 21:44 ` Lars Magne Ingebrigtsen
2003-02-23 9:51 ` Kai Großjohann
2003-02-22 22:33 ` Simon Josefsson [this message]
2003-02-23 9:52 ` Kai Großjohann
2003-02-23 11:04 ` Simon Josefsson
2003-02-23 13:33 ` Kai Großjohann
2003-02-23 16:56 ` Simon Josefsson
2003-02-23 17:23 ` Kai Großjohann
2003-02-23 11:34 ` Lars Magne Ingebrigtsen
2003-02-23 16:56 ` Michael Shields
2003-02-22 21:43 ` Paul Jarc
2003-02-23 5:03 ` Michael Shields
2003-02-23 10:28 ` Kai Großjohann
2003-02-23 11:38 ` Lars Magne Ingebrigtsen
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=ilur8a07xoj.fsf@latte.josefsson.org \
--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).