Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master

Mar 27, 2014

  1. Richard Huang

    Merge pull request #6 from vicentemundim/expire_restriction_keys

    Expiring restriction keys after their effective period has finished.
    authored March 27, 2014

Nov 05, 2011

  1. Vicente Mundim

    Expiring restriction keys after their effective period has finished.

    - This helps keeping redis resque namespace more clean, by using redis expire command to set an expiration for the restriction key by the same period of its effectiveness.
    - For example, if a job is restricted by minute, the first time that restriction key is set it will be marked to expire in 60 seconds, for a job that is restricted by hour it will be marked to expire after an hour, and so on.
    authored November 05, 2011

Nov 04, 2010

  1. Richard Huang

    Regenerated gemspec for version 0.3.0

    authored November 04, 2010
  2. Richard Huang

    Version bump to 0.3.0

    authored November 04, 2010
  3. Richard Huang

    rename identifier to restriction_identifier to solve the confliction …

    …with resque-retry
    authored November 04, 2010

Sep 09, 2010

  1. Richard Huang

    Regenerated gemspec for version 0.2.2

    authored September 09, 2010
  2. Richard Huang

    Version bump to 0.2.2

    authored September 09, 2010
  3. Richard Huang

    Merge branch 'backupify'

    authored September 09, 2010
  4. Matt Conway

    ignore rubymine files

    authored September 08, 2010
  5. Matt Conway

    make workers scan entire restriction queue rather than giving up afte…

    …r first one - this prevents workers from being under utilized
    authored September 08, 2010

Aug 10, 2010

  1. Matt Conway

    handle migration from single restriction queue

    authored August 10, 2010
  2. Matt Conway

    no need to check rest of settings if any prove job is restricted

    authored August 10, 2010
  3. Matt Conway

    segregate restirction queue based on original queue name

    authored August 10, 2010

Jul 09, 2010

  1. Richard Huang

    Regenerated gemspec for version 0.2.1

    authored July 10, 2010
  2. Richard Huang

    Version bump to 0.2.1

    authored July 10, 2010
  3. Matt Conway

    updates counts when there is a failure.

    authored July 09, 2010 flyerhzm committed July 10, 2010
  4. Matt Conway

    updates counts when there is a failure.

    authored July 09, 2010

Jun 29, 2010

  1. Matt Conway

    document concurrent option

    authored June 29, 2010
  2. Richard Huang

    update README

    authored June 29, 2010
  3. Richard Huang

    update README

    authored June 29, 2010
  4. Richard Huang

    Regenerated gemspec for version 0.2.0

    authored June 29, 2010
  5. Richard Huang

    Version bump to 0.2.0

    authored June 29, 2010
  6. Matt Conway

    fix requeuing

    authored June 29, 2010
  7. Matt Conway

    value stored should be number of jobs allowed to get "concurrent" per…

    …iod to work
    authored June 29, 2010
  8. Matt Conway

    add a concurrency limit

    authored June 28, 2010
  9. Matt Conway

    remove debug

    authored June 28, 2010
  10. Matt Conway

    Avoid race condition by using setnx/decr before job runs

    authored June 28, 2010
  11. Matt Conway

    Allow selection of custom identifiers

    authored June 28, 2010

Jun 28, 2010

  1. Matt Conway

    expire cannot be combined with incr: http://code.google.com/p/redis/w…

    authored June 28, 2010
  2. Matt Conway

    allow using as a module instead of by extension

    authored June 28, 2010

May 01, 2010

  1. Richard Huang

    add install to README

    authored May 01, 2010
  2. Richard Huang

    add gemspec

    authored May 01, 2010

Apr 30, 2010

  1. Richard Huang

    update README

    authored April 30, 2010
  2. Richard Huang

    update description in Rake file and README

    authored April 30, 2010
  3. Richard Huang

    use Resque.queue_from_class to get the job queue

    authored April 30, 2010
Something went wrong with that request. Please try again.