Updates:
Status: Invalid
Comment #1 on issue 330 by [email protected]: Large expiration values
result in no value being stored
http://code.google.com/p/memcached/issues/detail?id=330
Expiration times
----------------
Some commands involve a client sending some kind of expiration time
(relative to an item or to an operation requested by the client) to
the server. In all such cases, the actual value sent may either be
Unix time (number of seconds since January 1, 1970, as a 32-bit
value), or a number of seconds starting from current time. In the
latter case, this number of seconds may not exceed 60*60*24*30 (number
of seconds in 30 days); if the number sent by a client is larger than
that, the server will consider it to be real Unix time value rather
than an offset from current time.
For emphasis:
if the number sent by a client is larger than
that, the server will consider it to be real Unix time value rather
than an offset from current time.
To repeat:
If it's over 30 days, it treats it like a datetime in unix timestamp
format. So you can set larger values, but you have to treat them
differently.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
