> No question :) > It's just that this is what the original question was about and why I > suggested > doing his own sesssion timeout check as the deleting proccess is too > unreliable > to depend on for timeout handling. PHP will quite happily return stale > data > which could be bad in a login type of situation.
Okay. I think I thought you were the original poster. How do you know it's returning "stale" data, though? If the cookie is valid, and there is still a session file (or data in memory), then why is it stale or expired. Maybe I'm just missing something here. If it's expired because you think it's too old, then you track your own timestamps and do your own cleanup. Is that what you're saying? ---John Holmes... -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php