From: Charles Lindsey (chl@clw.cs.man.ac.uk)
Date: Tue Mar 07 2000 - 05:01:01 CST
In <873dq3ye3i.fsf@erlenstar.demon.co.uk> Andrew Gierth <andrew@erlenstar.demon.co.uk> writes:
> Charles> Anyway, I think the correct way for Replaces is that the
> Charles> slave has to do the work, as a byproduct of implementing the
> Charles> 'cancel' aspect of the Replaces header, as Brad has pointed
> Charles> out.
>Which is a royal pain, because it means that the slave has to rewrite
>the Xref header received from the master system.
Yes, this is the area that could be tricky (I think the problems of
getting the history file right, by use of duplicates or overwriting the
API are fixable).
Now AFAICS, all the relevant information is available when the master
delivers the article to the slave, so we are not asking the slave to
overwrite its Xref line after it has stored the article.
So the master says to the slave:
"here is an article"
"here is the groups and numbers it goes to" or "here is its Xref line"
"by the way, this cancels article <xxxx>"
or
"by the way, this replaces article <xxxx> - wou will need to augment the
Xref line I just sent"
Actually, with this setup, is it actually necessary to store the Xref line
with the article, or is it sufficient to store that information in the
overview?
-- Charles H. Lindsey ---------At Home, doing my own thing------------------------ Email: chl@clw.cs.man.ac.uk Web: http://www.cs.man.ac.uk/~chl Voice/Fax: +44 161 437 4506 Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K. PGP: 2C15F1A9 Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5