From 8530c24e8a1a5b83001ef1a851561bfd9d933880 Mon Sep 17 00:00:00 2001 From: Andrew Coleman Date: Mon, 22 Dec 2014 16:00:35 -0600 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7f91371..3afe59f 100644 --- a/README.md +++ b/README.md @@ -3,7 +3,7 @@ Uncomplicated Mutex A transactional mutex based in Redis for Ruby. It works across processes, threads, and machines provided you can all access the same Redis server. -This is subtely different from two related projects here on Github: kenn/redis-mutex and dv/redis-semaphore +This is subtely different from two related projects here on Github: https://github.com/kenn/redis-mutex and https://github.com/dv/redis-semaphore RedisMutex uses a polling interval and raises an exception on lock timeout. RedisSemaphore uses `blpop` to wait until a value is pushed into a list. I have noticed several issues with the two approaches. I have had jobs continue to run for days with RedisSemaphore due to random and unknown failures. RedisMutex raises an exception, and in my situation, I do not need an exception, I would prefer to assume that the previous job has failed and that execution should continue.