FREEBMD-SYNDICATES-L Archives

Archiver > FREEBMD-SYNDICATES > 2002-12 > 1039280760


From: "Bob Phillips" <>
Subject: Re: Syndicate management
Date: Sat, 7 Dec 2002 17:06:00 -0000
References: <000101c29d21$eeb1b360$c55a063e@slann> <3DF1CCCC.307DF4B7@the-harts.co.uk>


Hi Graham
This is a suggestion to get over the problem you mentioned in your mail.

extract from Graham's mail
"Range check must be completely rewritten and that will take some
> time to work out a way of providing the information without killing the
> servers. "

In the past I always assumed that the range check gave results based on
the last update and not necessarily current information. It doesn't matter
if this assumption is right or wrong. Cannot the range check (button 1 type
output) be performed after an update at a time when the server load is low
whenever that may be and the result stored. Then when a coordinator
requires the data it is then a simple data transfer rather than a large
search type operation.
I'd be quite prepared to use data that was a few weeks old as we don't
normally start the range check until the qtr/event is finished. An updated
file date would then be handy.
cheers
Bob Phillips

This thread: