_statuses uuid should not removed when expired but the status:uuid key-value exists

[comme]

when i set

Resque::Plugins::Status::Hash.expire_in = 60

and i create a job get uuid1 and do

loop { Resque::Plugins::Status::Hash.set(uuid1,"message") }

after 60 second i create another job,in resque-web statuses page i can't find uuid1's info but status:uuid still exists in redis.
so i think _statuses uuid should not removed when expired but the status:uuid key-value exists.

[quirkey]

@comme Ah, yeah - this makes sense. However, I think a cleaner way to do this would be to just update the score/timestamp with ZSET whenever a message is written to the status/uuid so ZREMRANGEBYSCORE still works as expected and you never have to loop through the entire ZSET (potentially really slow for a lot of statuses)

[comme]

@quirkey There is no ZSET command exists in redis but ZINCRBY and i don't think update the score/timestamp when a message is written to the status/uuid is a good solution, because after statuses expired (this periods of time i don't update uuid message) i call Resque::Plugins::Status::Hash.create before Resque::Plugins::Status::Hash.set the statuses will remove before you update the score/timestamp.