Update lonely_job to use new locking pattern

[joetastic]

This takes uses the new suggestion as specified at http://redis.io/commands/set

[wallace]

Sorry for the all the comment spam. I've researched the resque-lonely_job incompatibility with resque 1.25.x and it was due to the strict dependency on mock_redis.

I've released 1.0.1, the current HEAD of master and you'll want to rebase off of that. :)

If you can keep lock_timeout as part of the public API, that'd be great and I'd be happy to merge that in and release a 2.0.0 version of resque-lonely_job that changes its depedency to resque 1.21, which is when resque loosened its dependency on redis-namspace to 1.x which adds support for redis-rb 3.0.x. And redis-rb 3.0.5 is when support for Redis 2.6.12+ is added with SET and its arguments like NX.

Cheers!

[pboling]

@joetastic This looks like a great idea.

The supported fork of this project is resque-unique_at_runtime. I am the maintainer of both, and I will be releasing a new version of this gem with an upgrade path toward resque-unique_at_runtime.

I will look into adding this to resque-unique_at_runtime

Ref: #13