Printable View
I am working on a simple counter.
When the page is hit, a file is opened and records the hit (an invisible counter). However, I wish to prevent the counter from counting reloads but I don't want to use cookies. Is this possible? Or would I have to use sessions or stuff like that?
You'd probably have to use cookies to store whether or not the user has been counted. Or you could record their IP addresses (but dialup IPs don't stay the same)Quote:
Originally posted by evil_gamer
I am working on a simple counter.
When the page is hit, a file is opened and records the hit (an invisible counter). However, I wish to prevent the counter from counting reloads but I don't want to use cookies. Is this possible? Or would I have to use sessions or stuff like that?
You could even use sessions and track their session id, but sessions use cookies to work.
If you do track their IP, you probably want to chop off the last digit grouping. The reason? Many DHCP broadband companies change your IP but that last grouping, and it's rare that somebody else from within that grouping will get miscounted just given the traffic of the site.
sessions are easier and are stored on the server, not the client...
simple example.... this will work nicely.. that way you have no worries.....PHP Code:<?
session_start(); // this is what starts it all... before html!
if(!$logged) //check if a session is here
{
$logged = 1; // no session found...
session_register(logged); // make one ;)
}
else
{
// counter code here!
}
?>
But sessions use cookies (to track the session ID), so why not just use cookies to track whether or not they've been counted and skip the session crap? Makes more sense to me.Quote:
Originally posted by Iamryan2002
sessions are easier and are stored on the server, not the client...
simple example.... this will work nicely.. that way you have no worries.....PHP Code:<?
session_start(); // this is what starts it all... before html!
if(!$logged) //check if a session is here
{
$logged = 1; // no session found...
session_register(logged); // make one ;)
}
else
{
// counter code here!
}
?>
And just incase you want to argue that they don't use cookies:
Of course you can store it in the URL, but once they close the window, it's gone. Next time they come back, they're assigned a new session ID.Quote:
A visitor accessing your web site is assigned an unique id, the so-called session id. This is either stored in a cookie on the user side or is propagated in the URL.
either way...
What do you mean, either way? Sessions would need cookies to work, so if you're going to use cookies, why not just store it in the cookie?Quote:
Originally posted by Iamryan2002
either way...
I realize that sessions use cookies...
for a counter though, sessions are better... while you are at the site you are only one count, right.. well when you leave, the session is destroyed. You come back you are counted again.
Sessions will give you a much more accurate count, not cookies..
That's not counting unique visitors then...Quote:
Originally posted by Iamryan2002
I realize that sessions use cookies...
for a counter though, sessions are better... while you are at the site you are only one count, right.. well when you leave, the session is destroyed. You come back you are counted again.
Sessions will give you a much more accurate count, not cookies..
Off the top of my head, for daily uniques:
PHP Code:if (is_set($_COOKIE["countdate"])) {
if ($_COOKIE["countdate"] != date("m.d.y") {
//count the person for today
setcookie("countdate", date("m.d.y");
}
} else {
setcookie("countdate", date("m.d.y");
//count the person for today
}
that would work also... sessions, cookies, all good
shut upQuote:
Originally posted by Iamryan2002
that would work also... sessions, cookies, all good