Re: lynx-dev when, where, why "kb/sec"?

[David Woolley]

>  
> i haven't tried the dev versions yet,
> but i certainly prefer the present `milometer' presentation;
> i have never understood why sometimes it predicts the total, sometimes not:

A lot of pages are generated on the fly these days (e.g. to insert advertising)
and the server doesn't know the size when it generates the headers.

> having the total & the running count is a very good guide for `z'apping.
> there's surely room for adding  4 kb/sec  after the traditional count

Working out rates sensibly was too much for Microsoft; IE includes the
time taken to specify the destination file in the calculation!

Generally a sensible calculation is quite difficult because TCP produces
a lumpy data stream and, unless you go the Microsoft way, you need to take
a rolling average of several tens of K bytes to get a meaningful figure.