The central problem that this patch solves, is that
both Giganews and Usenetserver have started returning
"503 Timeout" when we take too long, say, to flush
headers. Making 503 non-fatal, or reducing the
"idletimout" to below a minute is not a complete fix
for the most active groups, however, as there are
*always* more headers to flush every minute, so the
cycle repeats indefinitely. There are four parts to
1) Make 503 non-fatal. (Closes bug 892418.)
2) Add a blank line before "Retrieving...". Without
that, we're clearing the "Flushing..." or GROUP reply
from the screen.
3) The main idea: only perform the time-consuming flush
once per session (per server, per group). The OVERVIEW
file will always be slightly out of sync on the server
itself, let alone the cached copy on the client, so
there really is no down side here.
4) While we're in here... permit the user to to limit
the number of articles requested and cached. This is an
oft-requested feature. (See bug 103887, RFE 1029939.)
My implemention is ngetrc-only. I don't see the point
to making it per-server, or permitting changing it on
the command line. A possible improvement would be to
make it per-group -- perhaps a user would like to pull
all the headers for a new group, and then trim it down
once he's caught up, or perhaps he'd like to make the
limit larger for a group that's carried on fewer
servers (to keep memory usage constant).
Log in to post a comment.