From: Rob Browning <rlb@defaultvalue.org>
Subject: Re: Question about article identification and backends.
Date: Sat, 17 May 2003 21:57:39 -0500 [thread overview]
Message-ID: <87d6iharmk.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87vfw9gszz.fsf@eris.void.at> (Andreas Fuchs's message of "Sat, 17 May 2003 21:29:43 +0000 (UTC)")
Andreas Fuchs <asf@void.at> writes:
>> the headers in the hash, at least for the UID), for most purposes, I
>> suspect even just a simple monotonically increasing integer serial
>> number would be sufficient.
>
> I fear not - concurrency issues would make the whole thing fall apart.
Certainly, but when I mentioned the monotonically increasing serial
number approach, I wasn't thinking about the RMS system. I was
thinking about a case where Gnus is the only one handling incoming
messages. i.e. an approach where there is no "Gnus unique number"
until Gnus assigns one. More specifically, I was thinking in terms of
an SQL serial column where the DB handles the concurrency issues. I
mentioned the RMS system primarily because it also discussed the
values of a permanent message ID (and because it sounds like an
interesting system). Though if implementing/using RMS, I probably
would want to include the headers in the hash (as they discuss
speculatively).
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next prev parent reply other threads:[~2003-05-18 2:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-17 19:56 Rob Browning
2003-05-17 21:29 ` Andreas Fuchs
2003-05-18 2:57 ` Rob Browning [this message]
2003-05-18 3:19 ` Rob Browning
2003-05-18 9:52 ` Kai Großjohann
2003-05-18 18:38 ` Rob Browning
2003-05-18 18:50 ` Rob Browning
2003-05-19 13:02 ` Kai Großjohann
2003-05-19 13:02 ` Kai Großjohann
2003-05-19 16:57 ` Paul Jarc
2003-05-19 16:47 ` Paul Jarc
2003-05-19 20:49 ` Kai Großjohann
2003-05-19 20:57 ` Paul Jarc
2003-05-20 10:56 ` Kai Großjohann
2003-05-20 17:33 ` Rob Browning
2003-05-22 7:04 ` 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=87d6iharmk.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.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).