Re: lynx-dev page counters

[Leonid Pauzner]

>>
>> i often see counters that hide behind images
>> could lynx implement an switch to load the first by fro such images

> Lynx has no way of distinguishing them from other images - you will have
> to load them yourself.

>> (it is not nice to not be counted as visiror ...)

> These are mainly a vanity feature; there are better ways of tracking
> visits, most of which put a lot less load on the internet than a forced
> end to end fetch.  (Someone with a serious need for the statistics is
> best advised to make one small item uncacheable++ temporarily and then
> examine the server logs and extrapolate the result to the case where
> all hits would have been logged.)

>> as i have understand the only counters that count with lynx
>> are the cgi that sits behind html files (installed in the web server)

> These are even worse than images, because the resulting pages tend to
> be even larger.

> Note all uncacheable content is annoying for people with metered phone
> calls and a local cache.


No, he mean a counter visible for user (client), not a web admin statistics,
the alternative for images here the dynamically generated HTML
which is uncachable anyway.
(another solution may be to track down info from HTTP headers
and use javascript on client side, I am not sure whether
HTTP 1.1 have an appropriate field or not).


> ++ Strictly speaking, it should be made to appear non-cacheable to HTTP 1.0
>    but actually be marked must-revalidate, so that HTTP 1.1 software sends
>    an If-Modified-Since request, but doesn't require the actual content back.
and so the HTTP 1.0