From: Andrew Gierth (andrew@erlenstar.demon.co.uk)
Date: Mon Mar 06 2000 - 15:37:37 CST
>>>>> "Charles" == Charles Lindsey <chl@clw.cs.man.ac.uk> writes:
>> The basic setup for an xref-slaved cluster is like this. You have a
>> hub system, which has a spool only as big as it needs (retention maybe
>> measured in hours at best), and no overviews. This takes incoming
>> articles from transit servers, allocates numbers to them using its
>> active file, generates Xref headers using those numbers, and feeds out
>> the articles to some number of reader boxes (which have big spools,
>> and overviews, but which use the article numbers from the Xref headers
>> rather than generating their own).
Charles> So the slave does not keep a history file?
where did I say that?
(I know of one setup where the slave does not have a conventional history
file, but that is orthogonal to this issue.)
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.
-- Andrew.