I forgot to mention, that this doesn't mean, you can not read data after
this timeout or that a session does ALWAYS die after this timeout. I would
assume, that the server has to have a reason to run garbage clean up. If the
server is not running a clean up, I would expect the session would excist
longer for access.
"Tom Worster" <f...@thefsb.org> wrote in message
> i'm not 100% sure what the manual means when it says...
> session.gc_maxlifetime integer
> session.gc_maxlifetime specifies the number of seconds after which data
> be seen as 'garbage' and cleaned up. Garbage collection occurs during
> session start.
> what event exactly does the "after which" here refer to?
> i'd like to think that it means that a session is eligible for gc no
> than session.gc_maxlifetime seconds after the most recent access (read or
> write) to that session. but it seems dangerously presumptuous to assume
> this is the case.
> what do you take it to mean?
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php