How is leafnode's delaybody supposed to work?

["Christian Pernegger" <pernegger@chello.at>]

I'd like to proxy news in a LAN with a potato server and 2 Windows clients.
Both low and high traffic text groups will be read and some binary groups
scavenged :)

The obvious choice for me was leafnode, BUT the standard mode where it gets
all messages in all groups is obviously to expensive in terms of bandwidth,
as well as ineffective - probably only 1/10th of all messages are actually
read.

In delaybody=1 mode it will download only headers, replace the bodies with a
pseudo-message comfirming it has been marked for the next retreival and
retreive the real body the next time fetchnews is run...

It says in the docs this doesn't work with Netscape, but it also doesn't
work properly with Forte Agent or XNews (=every reader with cache). Also,
I'd have to cron fetchnews every minute to allow the users normal reading.

Did I setup something wrong? If not, what would one use delaybody for?

And, most importantly, how can I achieve the desired effect: (not
necessarily with leafnode)

* clients can connect to the local "newsserver" and see the combined active
files of all configured servers

* headers are refreshed regularly and stored on the server

* as soon as a user requests a body, if is fetched and piped through from
the upstream server


Regards

Christian