resque-remote 0.1.1 → 0.1.2

data/Gemfile.lock

@@ -1,21 +1,21 @@
 PATH
   remote: .
   specs:
-    resque-remote (0.1.1)
-      resque (~> 1.0)
+    resque-remote (0.1.2)
+      resque (< 2.0)
 
 GEM
   remote: http://rubygems.org/
   specs:
     diff-lcs (1.1.3)
-    multi_json (1.3.6)
-    rack (1.4.1)
-    rack-protection (1.2.0)
+    multi_json (1.7.1)
+    rack (1.5.1)
+    rack-protection (1.3.2)
       rack
-    redis (3.0.1)
-    redis-namespace (1.2.0)
+    redis (3.0.3)
+    redis-namespace (1.2.1)
       redis (~> 3.0.0)
-    resque (1.21.0)
+    resque (1.23.1)
       multi_json (~> 1.0)
       redis-namespace (~> 1.0)
       sinatra (>= 0.9.2)
@@ -28,9 +28,9 @@ GEM
     rspec-expectations (2.8.0)
       diff-lcs (~> 1.1.2)
     rspec-mocks (2.8.0)
-    sinatra (1.3.2)
-      rack (~> 1.3, >= 1.3.6)
-      rack-protection (~> 1.2)
+    sinatra (1.3.4)
+      rack (~> 1.4)
+      rack-protection (~> 1.3)
       tilt (~> 1.3, >= 1.3.3)
     tilt (1.3.3)
     vegas (0.1.11)

data/README.md

@@ -6,7 +6,7 @@ Resque Remote's simple goal is to allow you to add a job to a queue with a strin
 
 # Installation
 
-**Note: You must have a version of Resque installed or added to your Gemfile for Resque Remote to work. Resque Version 0.10.0 has been tested to work with the current release of Resque Remote.**
+**NOTE: Resque-remote is compatible with Resque 1.x but unnececssary for >= 2.x. If you are using Resque 2.x, use the standard API method Resque.push instead.**
 
 Install the gem ad-hoc:
 
@@ -16,7 +16,7 @@ Install the gem ad-hoc:
 Or, add it to your Bundler `Gemfile`:
 
 	# Gemfile
-	gem 'resque', '0.10.0'
+	gem 'resque', '< 2.0'
 	gem 'resque-remote'
 
 And then run a `bundle install`.
@@ -33,11 +33,11 @@ If you're using bundler, just setup your gemset normally.
 ## (De)Queueing
 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, ...)
+	Resque.remote_enqueue('UpdateStockTicker', :ticker_low, param1, param2, ...)
 
 To dequeue, call `remote_dequeue` instead:
 
-	Resque.remote_dequeue('MyJobClass', :low_priority, param1, param2, ...)
+	Resque.remote_dequeue('UpdateStockTicker', :ticker_low, param1, param2, ...)
 
 ## Worker processing
 
@@ -45,7 +45,7 @@ Resque Remotes purpose is to make remote job processing doable. Hence, your work
 
 Note that the queue this job belongs to isn't defined in our job class because it's metadata that Resque uses when it first queues the job, which we've already done. So, no `@queue = :low_priority` needed here.
 
-	class MyJobClass
+	class UpdateStockTicker
 		# no queue needed
 
 		def self.perform(param1, param2)

data/lib/resque-remote/version.rb

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

data/resque-remote.gemspec

@@ -8,8 +8,10 @@ Gem::Specification.new do |s|
   s.authors     = ['BJ Neilsen']
   s.email       = ['bj.neilsen@gmail.com']
   s.homepage    = 'http://github.com/localshred/resque-remote'
-  s.summary     = 'Resque plugin to allow remote job droppability'
+  s.summary     = 'Resque plugin to allow remote job droppability compatible with Resque 1.x'
   s.description = %Q{
+Compatible with Resque 1.x. Use Resque.push if you are using >= 2.x.
+
 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
@@ -27,7 +29,7 @@ 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.0'
+  s.add_dependency 'resque', '< 2.0'
 
   s.add_development_dependency 'bundler', '~> 1.0'
   s.add_development_dependency 'rspec', '~> 2.8'

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: resque-remote
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.1.2
   prerelease: 
 platform: ruby
 authors:
@@ -9,22 +9,27 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-07-27 00:00:00.000000000Z
+date: 2013-03-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: resque
-  requirement: &2156201460 !ruby/object:Gem::Requirement
+  requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
-    - - ~>
+    - - <
       - !ruby/object:Gem::Version
-        version: '1.0'
+        version: '2.0'
   type: :runtime
   prerelease: false
-  version_requirements: *2156201460
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - <
+      - !ruby/object:Gem::Version
+        version: '2.0'
 - !ruby/object:Gem::Dependency
   name: bundler
-  requirement: &2156200900 !ruby/object:Gem::Requirement
+  requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
@@ -32,10 +37,15 @@ dependencies:
         version: '1.0'
   type: :development
   prerelease: false
-  version_requirements: *2156200900
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '1.0'
 - !ruby/object:Gem::Dependency
   name: rspec
-  requirement: &2156200440 !ruby/object:Gem::Requirement
+  requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
@@ -43,9 +53,17 @@ dependencies:
         version: '2.8'
   type: :development
   prerelease: false
-  version_requirements: *2156200440
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '2.8'
 description: ! '
 
+  Compatible with Resque 1.x. Use Resque.push if you are using >= 2.x.
+
+
   Resque is great. So is job processing with redis. Our biggest drawback has been
   that
 
@@ -110,9 +128,9 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: 1.3.6
 requirements: []
 rubyforge_project: resque-remote
-rubygems_version: 1.8.15
+rubygems_version: 1.8.24
 signing_key: 
 specification_version: 3
-summary: Resque plugin to allow remote job droppability
+summary: Resque plugin to allow remote job droppability compatible with Resque 1.x
 test_files: []
 has_rdoc: