script for counting the no. of enters on the site

[Mr. x]

Hello,
I need a script for counting the no. of enters on my site, please.

I need a check that for the same user in the same day - if the user enter
several times, it is count once
(or something like this - I need that the script will accurate as possible).

On the server side I have the .NET server.

Thanks

 

[Michael Winter]

on 15/11/2003:

Hello,
I need a script for counting the no. of enters on my site, please.

I need a check that for the same user in the same day - if the user enter
several times, it is count once
(or something like this - I need that the script will accurate as possible).

On the server side I have the .NET server.

Do this server-side. You won't be able to store the results with
JavaScript.

Alternatively, just use a free web statistics service.

Mike

 

[Evertjan.]

Mr. x wrote on 15 nov 2003 in comp.lang.javascript:

I need a check that for the same user in the same day - if the user enter
several times, it is count once

Even serverside, you cannot detect a user reliably, unless you can set a
cookie on his machine. Clientside, there is no way to store the count of
the other users.

On the server side I have the .NET server.

Better ask a dotnet group.

 

[Dr John Stockton]

JRS: In article <[email protected]>, seen in

Mr. x wrote on 15 nov 2003 in comp.lang.javascript:

Even serverside, you cannot detect a user reliably, unless you can set a
cookie on his machine. Clientside, there is no way to store the count of
the other users.

Not even then; think about "his". Our Public Library has more than a
score of machines, and I could use each in turn. If they accept
cookies, they are probably configured not to retain them between user
sessions.

Alternatively, after he has used "his" machine, his entire family might
also use it.

 

[Evertjan.]

Dr John Stockton wrote on 16 nov 2003 in comp.lang.javascript:

Not even then; think about "his". Our Public Library has more than a
score of machines, and I could use each in turn. If they accept
cookies, they are probably configured not to retain them between user
sessions.

John, I would count that as different users.

.. his entire family might also use it.

... so we are back to the undefined entity "user".

 

[Thomas 'PointedEars' Lahn]

I need a script for counting the no. of enters on my site, please.

You do not need and you do not want this, not even server-side.
Counters are a Bad Thing (feed the words to Google for proof,)
use tools that evaluate server logs instead.


PointedEars

 

[Dr John Stockton]

JRS: In article <[email protected]>, seen in
Thomas 'PointedEars' Lahn

You do not need and you do not want this, not even server-side.
Counters are a Bad Thing (feed the words to Google for proof,)
use tools that evaluate server logs instead.

Do not presume that server logs are available.

Page counters give usable information, provided that the numbers are
interpreted cautiously. For example, if I were to put counters on the
Date/Time and Javascript portions of my site, I could get a fair
estimate of their relative popularity - especially if the numbers were
very different.

 

[Thomas 'PointedEars' Lahn]

Do not presume that server logs are available.

Page counters give usable information, provided that the numbers are
interpreted cautiously. For example, if I were to put counters on the
Date/Time and Javascript portions of my site, I could get a fair
estimate of their relative popularity - especially if the numbers were
very different.

In most cases either the logs are available directly or the service provider
provides tools to evaluate them (for example a web interface). Even if
nothing of that applies, and the cookie nagging of free counters aside, I
strongly recommend not to have a *visible* counter on the site at least.
Showing the numbers tells the visitor much about the author's character
because if the numbers are low in most cases the reason is obvious --
naive-dumb ways of authoring, ignoring the nature if the Web. I have never
seen a (semi-)professional putting a counter on their web site or even
heard/read recommending it. On the other hand, those numbers can be faked,
too. Do not expect a visitor to cry out "Hooray! That site -- so many
people have visited it, it must be good! I am not wasting my time here!!1".


PointedEars

 

[Dr John Stockton]

JRS: In article <[email protected]>, seen
in Thomas 'PointedEars' Lahn

In most cases either the logs are available directly or the service provider
provides tools to evaluate them (for example a web interface). Even if
nothing of that applies, and the cookie nagging of free counters aside, I
strongly recommend not to have a *visible* counter on the site at least.
Showing the numbers tells the visitor much about the author's character
because if the numbers are low in most cases the reason is obvious --
naive-dumb ways of authoring, ignoring the nature if the Web. I have never
seen a (semi-)professional putting a counter on their web site or even
heard/read recommending it. On the other hand, those numbers can be faked,
too. Do not expect a visitor to cry out "Hooray! That site -- so many
people have visited it, it must be good! I am not wasting my time here!!1".

You are again being pointless.

Such logging is not necessarily available. Your "most cases" is not the
same as "all cases".

Free counters do not necessarily require either cookies or nagging. For
example, my ISP supplies one (but supplies only minimal logging) with my
type of account. If you're clever enough to find where on my site the
counter is, you might even be able to read its value, but don't ask for
details since I read it by a means not available to you.

The OP wants to discover some form of count; you should not introduce
the idea of displaying the counter to the general public just in order
to denigrate said idea.