Description: ------------ In HTTP_Session_Container_Memcache:write the expire date is calculated as follows: time() + ini_get('session.gc_maxlifetime') Now when server clocks should be different (I had such a case lately), we get a bug that is very hard to detect. In http://www.php.net/manual/en/function.memcache-set.php expire: ..... You can also use Unix timestamp or a number of seconds starting from current time, but in the latter case the number of seconds may not exceed 2592000 (30 days). So if ini_get('session.gc_maxlifetime')<2592000 then it should be 0++ ini_get('session.gc_maxlifetime') to make use of memcache server time.

I meant 0+ini_get('session.gc_maxlifetime')

I'd suggest implementing some kind of way to setTime() around here might not hurt - if not nothing else, just to make it more unit testable.

Given HTTP_Session2 superceeds HTTP_Session, is this feature request still relevant? If not, we should close this.

Wait, people need a workaround in a class when the server time is broken? The fix is called NTP in this case. :D In all seriousness though - setTime(), getTime() is a good idea for unit testing. I'll see to it for the 0.8.0 release. @Daniel: I'll email you when it's in trunk so you can verify it to your liking.

Hey guys, I committed some additions: http://svn.php.net/viewvc?view=revision&revision=303025 Please check it out and let me know what you think. Till

This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.