From: Dave Barr (barr@cis.ohio-state.edu)
Date: Wed Sep 16 1998 - 17:10:01 CDT
>2. The History file of the server contains entries for BOTH IDs, the
Don't say "The History file". Not only is it implementation-specific,
but it's wrong for INN and C-news. I don't forsee the history file
being modified to accomodate a P-ID, notwithstanding the fact that
dbz precludes this from working.
INN would implement it with another database (not dbz) with P-ID->M-ID
mappings.
>4. Initial posting of Named article (i.e. one which contains a Named:
>header, and provides both an M-ID and a P-ID, even if they are identical
>on the first occasion).
>
> If P-ID already exists in the History file, then report Error and
Shouldn't that be "M-ID"? Posting a message with an existing P-ID
is not an error--it's by design.
Delete (4) since it's redundant with existing practice.
> reject. Else create History file entries under both M-ID and P-ID
> (or just the one if they are identical) and store article with new
> Xref numbers for each group.
>
>5. Cancel of Named article (cancel command uses the M-ID)
Same with (5).. there's no changes in cancels so there's no need to
mention it.
>6. Supersedes of an ordinary article (i.e. replacing article has no Named:
>header).
Same again.
--Dave