From: Andrew Gierth (andrew@erlenstar.demon.co.uk)
Date: Fri Mar 03 2000 - 13:47:09 CST
>>>>> "Brad" == Brad Templeton <brad@templetons.com> writes:
>> And this is the other part I have a problem with - in a cluster
>> system the Xref is generated in the hub, and so this step fails if
>> the article being replaced has expired from the hub's spool (which
>> is small compared to that of the reader systems).
Brad> Does that mean it leaves the hub's history file too?
No, but the history file doesn't have article numbers in.
Brad> Anyway, I guess it means that the tools that actually generate
Brad> the article number have to generate the xref. Is this not
Brad> possible in your design?
The hub assigns the article numbers (how else is it going to generate
the Xref?)
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).
-- Andrew.