From: Charles Lindsey (chl@clw.cs.man.ac.uk)
Date: Mon Mar 06 2000 - 05:07:56 CST
In <873dq7bzuq.fsf@erlenstar.demon.co.uk> Andrew Gierth <andrew@erlenstar.demon.co.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).
So the slave does not keep a history file? In that case, suppose a client
of the slave does an NNTP ARTICLE <msgid> (perhaps in connection with a
<news:mesgid> URL it found somewhere). What happens then?
Anyway, I think the correct way for Replaces is that the slave has to do
the work, as a byproduct of implementing the 'cancel' aspect of the
Replaces header, as Brad has pointed out.
-- 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