Marek Kilimajer schrieb:
Hendrik Schmieder wrote:
Marek Kilimajer schrieb:
Hendrik Schmieder wrote:
Hello,
we have a severe problem with seesions.
We use Apache 1.3.31 with PHP 4.3.9 as Apache module in Windows 2000
In our php.ini we have
session.gc_probability = 100 session.gc_dividend = 100
Should be session.gc_divisor
OK , changed in php.ini, but no change in behaviour.
And you need to start at least one other session so that the first one gets cleared.
If you are right, then this is a severe design bug.
Depends on your point of view. It is a sideeffect of loading current session (and thus accessing it) before the session gc is called.
So the question is, should the session module give up on current session just because it should have been garbaged, even if the session file still exists?
That's the point.
If the current sesions timed out, since there was no action in the session lifetime, then the session file must be deleted.
On the other side, if there's an action in the session lifetime, the timer for this session should be reset to zero.
Anyway , if the apache service is stopped (I am not speaking about a crash) all session files must be deleted.
Hendrik
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
