Updates:
Owner: [email protected]
Comment #1 on issue 169 by [email protected]: probably incorrect treatment
of negative expiration time
http://code.google.com/p/memcached/issues/detail?id=169
I toyed with this a bit and it'd be fun to fix I think.
It's actually doing something pretty bizarre:
- start memcached
- immediately set an item with an expiration time of -30
- item will exist until roughly 30 seconds have passed
- do it again, with a time of -30
- item will not exist
- set an expiration time of -60
- item will exist for the next 30 seconds.
basically it ends up subtracting from the process start time. It *should*
work in that anything negative immediately expires, which makes add lock
testing more useful, but unfortunately I think binprot uses a signed value
for expiration. so we'll have to think about that.
