The fault with this is that unless you use session unique session ids to track visitors on your website and store these in the log file you have to make assumptions:
If I see the client IP is a.b.c.d and the next hit is from a.b.c.d then he must be the same visitor. (oops what about proxy servers? AOL? MSN? woopsie.)

If I see a delay of X minutes between hits then I am going to count this client IP as a new visitor, otherwise it is the same session and the session length is <time of last hit> - <time of first hit in session> long.

Depending on what level of accuracy you are looking for (and what percentage of your hits come from proxies) looking at the log files for this information just gives you faulty info.


-Waswas

In reply to Re: Re: viewer eyeball counter? by waswas-fng
in thread viewer eyeball counter? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.