session.gc_maxlifetime should always be a relative value.

[ianmaddox]

Without the addition of time(NULL), any value greater than 2678400 (30 days)
is treated as absolute. A 31 day gc_maxlifetime would result in empty sessions
because the memcached data is immediately timed out.

introduced in commit 39d0bee
fixes #142

[mkoppanen]

Am I to understand that the functionality has been released in 2.2.0 and the latest stable?

[ianmaddox]

Yes, I believe that is correct. I've actually run into this issue a few
times in the past several years, but always figured someone else would
handle it.
On Jul 15, 2014 6:22 PM, "Mikko Koppanen" notifications@github.com wrote:

Am I to understand that the functionality has been released in 2.2.0 and
the latest stable?

—
Reply to this email directly or view it on GitHub
#143 (comment)
.

[isotopp]

Why is this pull request abandoned? It should have been merged a year ago.

[sodabrew]

One problem now is that some consumers of this library add their own timestamps to work around the removal of the time(NULL) in the php-memcached module.

Another problem is that the semantics of memcached itself specifically define 30-days as the transition point from relative time in seconds to absolute time in epoch seconds. The previous behavior was tripping up people who were providing absolute times.

A reasonable heuristic might be to add time(NULL) only if the timestamp is less than one billion. The epoch time for January 2017 starts around 1.483 billion.

[sodabrew]

And as it turns out, almost exactly that idea was implemented in 27a22f3. Closing as resolved!