resque-remote 0.1.0 → 0.1.1

data/Gemfile.lock

@@ -1,23 +1,23 @@
 PATH
   remote: .
   specs:
-    resque-remote (0.1.0)
-      resque (< 1.18.0)
+    resque-remote (0.1.1)
+      resque (~> 1.0)
 
 GEM
   remote: http://rubygems.org/
   specs:
     diff-lcs (1.1.3)
-    json (1.5.4)
+    multi_json (1.3.6)
     rack (1.4.1)
     rack-protection (1.2.0)
       rack
-    redis (2.2.2)
-    redis-namespace (1.0.3)
-      redis (< 3.0.0)
-    resque (1.17.1)
-      json (>= 1.4.6, < 1.6)
-      redis-namespace (~> 1.0.2)
+    redis (3.0.1)
+    redis-namespace (1.2.0)
+      redis (~> 3.0.0)
+    resque (1.21.0)
+      multi_json (~> 1.0)
+      redis-namespace (~> 1.0)
       sinatra (>= 0.9.2)
       vegas (~> 0.1.2)
     rspec (2.8.0)

data/README.md

@@ -1,9 +1,6 @@
-> **Please note that Resque Remote depends on Resque versions < 1.18.0. resque-remote is not necessary in Resque >= 1.18 as `Resque.enqueue_at` became a standard
-API method which does exactly what resque-remote aims to provide.**
-
 Resque Remote is a plugin to allow remote job droppability. Try saying that 10 times fast.
 
-Resque is great and so is queue-based job processing with redis. Resque Remote aims to provide you the ability to queue a job without having the processing class (e.g. the Job handler itself) loaded into memory. 
+Resque is great and so is queue-based job processing with redis. Resque Remote aims to provide you the ability to queue a job without having the processing class (e.g. the Job handler itself) loaded into memory.
 
 Resque Remote's simple goal is to allow you to add a job to a queue with a string identifier for the class rather than the class constant. It is assumed that the worker-side of the equation _will_ have the class in memory and hence will be able to run it no problem. If this isn't the case, the worker will explode in a fiery ball. Probably getting some on you as a result.
 
@@ -15,20 +12,20 @@ Install the gem ad-hoc:
 
 	$ gem install resque -v 0.10.0
 	$ gem install resque-remote
-	
+
 Or, add it to your Bundler `Gemfile`:
 
 	# Gemfile
 	gem 'resque', '0.10.0'
 	gem 'resque-remote'
-	
+
 And then run a `bundle install`.
-	
+
 Without Bundler, in your appropriate config location for your app:
 
 	require 'resque'
 	require 'resque-remote'
-	
+
 If you're using bundler, just setup your gemset normally.
 
 # Usage
@@ -37,11 +34,11 @@ If you're using bundler, just setup your gemset normally.
 To queue a job, tell resque to `remote_enqueue` your job by passing the string representation of your job's class name, the name of the queue to use, and whatever parameters are appropriate for the job.
 
 	Resque.remote_enqueue('MyJobClass', :low_priority, param1, param2, ...)
-	
+
 To dequeue, call `remote_dequeue` instead:
 
 	Resque.remote_dequeue('MyJobClass', :low_priority, param1, param2, ...)
-	
+
 ## Worker processing
 
 Resque Remotes purpose is to make remote job processing doable. Hence, your workers won't be running the same application code that actually queued the job for you in the first place. So, assuming I queued the jobs from above, your separate application should have an implementing class that your workers have access to.
@@ -50,7 +47,7 @@ Note that the queue this job belongs to isn't defined in our job class because i
 
 	class MyJobClass
 		# no queue needed
-		
+
 		def self.perform(param1, param2)
 			# ... process the job herre
 		end

data/lib/resque-remote/version.rb

@@ -1,7 +1,7 @@
 module Resque
 	module Plugins
 	  module Remote
-	    VERSION = "0.1.0"
+	    VERSION = "0.1.1"
 	  end
 	end
 end

data/resque-remote.gemspec

@@ -10,11 +10,8 @@ Gem::Specification.new do |s|
   s.homepage    = 'http://github.com/localshred/resque-remote'
   s.summary     = 'Resque plugin to allow remote job droppability'
   s.description = %Q{
-Note: Resque-remote is not needed in resque >= 0.18 as `enqueue_at` became a standard
-API method which does exactly what resque-remote aims to provide.
-
 Resque is great. So is job processing with redis. Our biggest drawback has been that
-resque requires the class that will be processing a job to be loaded when the job 
+resque requires the class that will be processing a job to be loaded when the job
 is enqueued. But what happens when the implementing job is defined in a separate application
 and isn't currently loaded into memory?
 
@@ -30,13 +27,10 @@ Feedback, comments and questions are welcome at bj [dot] neilsen [at] gmail [dot
   s.required_rubygems_version = '>= 1.3.6'
   s.rubyforge_project         = 'resque-remote'
 
-  s.add_dependency 'resque', '< 1.18.0'
-  
+  s.add_dependency 'resque', '~> 1.0'
+
   s.add_development_dependency 'bundler', '~> 1.0'
   s.add_development_dependency 'rspec', '~> 2.8'
-  # s.add_development_dependency 'redis'
-  # s.add_development_dependency 'redis-namespace'
-  # s.add_development_dependency 'yajl-ruby'
 
   s.files        = `git ls-files`.split("\n")
   s.require_path = 'lib'

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: resque-remote
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
   prerelease: 
 platform: ruby
 authors:
@@ -9,22 +9,22 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-02-06 00:00:00.000000000Z
+date: 2012-07-27 00:00:00.000000000Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: resque
-  requirement: &2153289880 !ruby/object:Gem::Requirement
+  requirement: &2156201460 !ruby/object:Gem::Requirement
     none: false
     requirements:
-    - - <
+    - - ~>
       - !ruby/object:Gem::Version
-        version: 1.18.0
+        version: '1.0'
   type: :runtime
   prerelease: false
-  version_requirements: *2153289880
+  version_requirements: *2156201460
 - !ruby/object:Gem::Dependency
   name: bundler
-  requirement: &2153288740 !ruby/object:Gem::Requirement
+  requirement: &2156200900 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
@@ -32,10 +32,10 @@ dependencies:
         version: '1.0'
   type: :development
   prerelease: false
-  version_requirements: *2153288740
+  version_requirements: *2156200900
 - !ruby/object:Gem::Dependency
   name: rspec
-  requirement: &2153287300 !ruby/object:Gem::Requirement
+  requirement: &2156200440 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
@@ -43,17 +43,36 @@ dependencies:
         version: '2.8'
   type: :development
   prerelease: false
-  version_requirements: *2153287300
-description: ! "\nNote: Resque-remote is not needed in resque >= 0.18 as `enqueue_at`
-  became a standard\nAPI method which does exactly what resque-remote aims to provide.\n\nResque
-  is great. So is job processing with redis. Our biggest drawback has been that\nresque
-  requires the class that will be processing a job to be loaded when the job \nis
-  enqueued. But what happens when the implementing job is defined in a separate application\nand
-  isn't currently loaded into memory?\n\nEnter Resque Remote.\n\nResque Remote's simple
-  goal is to allow you to add a job to a queue with a string\nidentifier for the class
-  rather than the class constant. It is assumed that the worker-side of\nthe equation
-  _will_ have the class in memory and hence will be able to run it no problem.\n\nFeedback,
-  comments and questions are welcome at bj [dot] neilsen [at] gmail [dot] com.\n"
+  version_requirements: *2156200440
+description: ! '
+
+  Resque is great. So is job processing with redis. Our biggest drawback has been
+  that
+
+  resque requires the class that will be processing a job to be loaded when the job
+
+  is enqueued. But what happens when the implementing job is defined in a separate
+  application
+
+  and isn''t currently loaded into memory?
+
+
+  Enter Resque Remote.
+
+
+  Resque Remote''s simple goal is to allow you to add a job to a queue with a string
+
+  identifier for the class rather than the class constant. It is assumed that the
+  worker-side of
+
+  the equation _will_ have the class in memory and hence will be able to run it no
+  problem.
+
+
+  Feedback, comments and questions are welcome at bj [dot] neilsen [at] gmail [dot]
+  com.
+
+'
 email:
 - bj.neilsen@gmail.com
 executables: []
@@ -91,7 +110,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: 1.3.6
 requirements: []
 rubyforge_project: resque-remote
-rubygems_version: 1.8.10
+rubygems_version: 1.8.15
 signing_key: 
 specification_version: 3
 summary: Resque plugin to allow remote job droppability