I've seen this topic discussed before, but I don't think I've ever seen a straight answer.
I've heard that the expiration date you use with setcookie() uses the server's clock, but the cookie actually expires based on client's clock. This could cause problems if the two were in different time zones. On my first site, I just set the expiration date so far in the future that it wouldn't be a problem. However on my new site, I want the expiration date to reflect on how long a session can be idle (ie, not navigating around any pages on the site) before it is considered inactive and would be ended (if the cookie with the sid expired, it wouldn't be able to be passed back to the server to be validated and the user would be essentially logged off). Having an expiration/idle time of an hour would be a problem if time zones or DST were a factor.
At this point I'm thinking of just screwing the use of cookies on my site, passing all needed info on the URL, and logging when the user's last activity was so that I can see if it's been more than an hour and acting accordingly.
So which way does it work?