em-resque 1.0.2 → 1.0.3

data/README.markdown

@@ -8,6 +8,8 @@ forking a new one for every job. It can run N workers inside one process, it
 packs all of them in Ruby fibers. The library is meant for small but IO-heavy
 jobs, which won't use much of CPU power in the running server.
 
+Read the blog post [Resque with EventMachine][4] about solving our problems with this gem.
+
 Use cases
 ---------
 
@@ -36,9 +38,9 @@ class Pinger
   @queue = :ping_publisher
 
   def self.perform(url)
-    self.url = url
-    self.result = EventMachine::HttpRequest.new(url).get.response
-    self.save
+    res = Result.new
+    res.http_result = EventMachine::HttpRequest.new(url).get.response
+    res.save
   end
 end
 ```
@@ -108,13 +110,6 @@ when the main process terminates. The default value is 1.
 
     $ QUEUE=ping_publisher FIBERS=50 rake em_resque:work
 
-### The amount of green threads
-
-EventMachine has an option to use defer for long-running processes to be run in
-a different thread. The default value is 20.
-
-    $ QUEUE=ping_publisher CONCURRENCY=20 rake em_resque:work
-
 ### Signals
 
 EM:Resque workers respond to a few different signals:
@@ -273,3 +268,4 @@ Julius de Bruijn :: julius.bruijn@sponsorpay.com :: @pimeys
 [1]: http://rubyeventmachine.com/
 [2]: https://github.com/igrigorik/em-synchrony
 [3]: https://github.com/brianmario/mysql2/blob/master/lib/mysql2/em.rb
+[4]: http://sponsorpay.github.com/blog/2012/01/03/resque-with-eventmachine/

data/lib/em-resque/version.rb

@@ -1,5 +1,5 @@
 module EventMachine
   module Resque
-    Version = VERSION = '1.0.2'
+    Version = VERSION = '1.0.3'
   end
 end

data/lib/em-resque/worker_machine.rb

@@ -56,7 +56,6 @@ module EventMachine
       # Stop the machine.
       def stop
         @workers.each(&:shutdown)
-        File.delete(@pidfile) if @pidfile
       end
 
       def fibers

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: em-resque
 version: !ruby/object:Gem::Version
-  version: 1.0.2
+  version: 1.0.3
   prerelease: 
 platform: ruby
 authors:
@@ -9,11 +9,11 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-01-25 00:00:00.000000000 Z
+date: 2012-02-14 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: resque
-  requirement: &6582380 !ruby/object:Gem::Requirement
+  requirement: &21392500 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
@@ -21,10 +21,10 @@ dependencies:
         version: 1.19.0
   type: :runtime
   prerelease: false
-  version_requirements: *6582380
+  version_requirements: *21392500
 - !ruby/object:Gem::Dependency
   name: em-synchrony
-  requirement: &6581420 !ruby/object:Gem::Requirement
+  requirement: &21392000 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
@@ -32,10 +32,10 @@ dependencies:
         version: 1.0.0
   type: :runtime
   prerelease: false
-  version_requirements: *6581420
+  version_requirements: *21392000
 - !ruby/object:Gem::Dependency
   name: em-redis
-  requirement: &6580460 !ruby/object:Gem::Requirement
+  requirement: &21391440 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
@@ -43,7 +43,7 @@ dependencies:
         version: 0.3.0
   type: :runtime
   prerelease: false
-  version_requirements: *6580460
+  version_requirements: *21391440
 description: ! "    Em-resque is a version of Resque, which offers non-blocking and
   non-forking\n    workers. The idea is to have fast as possible workers for tasks
   with lots of\n    IO like pinging third party servers or hitting the database.\n\n