resque-jobs-per-fork 0.5.0 → 1.15.1

data/README.rdoc

@@ -1,6 +1,7 @@
 = resque-jobs-per-fork
 
 If you have very frequent and fast resque jobs, the overhead of forking and running your after_fork hook, might get too big. Using this resque plugin, you can have your workers perform more than one job, before terminating.
+The original use case for this project was keeping connections while fetching data from a very fragile and crappy webservice.
 
 You simply specify the number of jobs you want each fork to run using the JOBS_PER_FORK environment variable:
 
@@ -15,11 +16,12 @@ This plugin also defines 2 new hooks that get called after the fork starts and b
   Resque.before_perform_jobs_per_fork do |worker|
     worker.log("Your message here")
   end
-  
+
   Resque.after_perform_jobs_per_fork do |worker|
     worker.log("Your message here")
   end
 
+Version 1.15.x works on Resque 1.15.x
 Version 0.5.x works on Resque 1.11.x
 Version 0.4.x works on Resque 1.10.x 
 Version 0.3.x works on Resque 1.8.x 

data/lib/resque-jobs-per-fork.rb

@@ -3,7 +3,7 @@ require 'resque/worker'
 
 
 module Resque
-  
+
   # the `before_perform_jobs_per_fork` hook will run in the child perform
   # right before the child perform starts
   #
@@ -17,7 +17,7 @@ module Resque
   def self.before_perform_jobs_per_fork=(before_perform_jobs_per_fork)
     @before_perform_jobs_per_fork = before_perform_jobs_per_fork
   end
-  
+
   # the `after_perform_jobs_per_fork` hook will run in the child perform
   # right before the child perform terminates
   #
@@ -26,14 +26,14 @@ module Resque
   def self.after_perform_jobs_per_fork(&block)
     block ? (@after_perform_jobs_per_fork = block) : @after_perform_jobs_per_fork
   end
-  
+
   # Set the after_perform_jobs_per_fork proc.
   def self.after_perform_jobs_per_fork=(after_perform_jobs_per_fork)
     @after_perform_jobs_per_fork = after_perform_jobs_per_fork
   end
-  
+
   class Worker
-    
+
     def perform_with_jobs_per_fork(job)
       raise "You need to set JOBS_PER_FORK on the command line" unless ENV['JOBS_PER_FORK']
       run_hook :before_perform_jobs_per_fork, self

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: resque-jobs-per-fork
 version: !ruby/object:Gem::Version 
-  hash: 11
+  hash: 41
   prerelease: 
   segments: 
-  - 0
-  - 5
-  - 0
-  version: 0.5.0
+  - 1
+  - 15
+  - 1
+  version: 1.15.1
 platform: ruby
 authors: 
 - Sam Granieri
@@ -16,23 +16,23 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2011-02-24 00:00:00 -06:00
+date: 2011-05-09 00:00:00 -05:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
-  prerelease: false
-  type: :runtime
-  requirement: &id001 !ruby/object:Gem::Requirement 
+  version_requirements: &id001 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - ~>
       - !ruby/object:Gem::Version 
-        hash: 27
+        hash: 17
         segments: 
         - 1
-        - 10
-        version: "1.10"
-  version_requirements: *id001
+        - 15
+        version: "1.15"
+  prerelease: false
+  type: :runtime
+  requirement: *id001
   name: resque
 description: When your resque jobs are frequent and fast, the overhead of forking and running your after_fork might get too big.
 email: 
@@ -80,7 +80,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
 requirements: []
 
 rubyforge_project: 
-rubygems_version: 1.5.2
+rubygems_version: 1.6.2
 signing_key: 
 specification_version: 3
 summary: Have your resque workers process more that one job