tennis-jobs 0.2.0 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 41fd5c9ff7ba286a975e7f6fd69b422564884783
-  data.tar.gz: 02f1abfb9d8045033ab9bc8203b0d05473d4736e
+  metadata.gz: cbb90feec2f2e77454b97d27427725c8a742f43d
+  data.tar.gz: 116901e81bdb636395102e79e154b3237055b216
 SHA512:
-  metadata.gz: 37dda9596db258dea9c2eb3787bf1b674cca4faa3b4467cca957bd646f7d6ab6e8e76ef3382d8ac9b29f3afa0d73524224094b9b32cd493106061f4e021672cc
-  data.tar.gz: 67dddffbe9393ca3051eea299dcb95974f3a147ba31403070663fe534fce849a68752d33adf28be4a73ffe8dc2ab59478e5a2b42aec383089dea056317b0dc21
+  metadata.gz: 27600764daf9001be443cfea63c92933bb6dd4a0a234192fd12ed9087f8f1967df6f0f8d582ed9aedcc5e53ce7ae08a495edaefc787fc55ffb1a4df7bcdd9281
+  data.tar.gz: b3e4e2cf9fc030865c71b72817e4af930bfffd0ebfe92bcc21b7e4489fe629a9018e9320aac1f56f6827b6f8ebbf92d39e2b4556a53d340915329ec37eb79fe7

data/README.markdown

@@ -45,7 +45,7 @@ command:
 The `workers` options is directly given to sneakers, it will determine the
 number of subprocesses that will handle the messages, the level of parallelism.
 
-The classes are the classes that will receive your `execute` or `defer` calls
+The classes are the classes that will receive your `send_work` or `defer` calls
 but we'll see that later...
 
 Also it is possible to add options directly in your workers:
@@ -97,7 +97,7 @@ class MyClass
   end
 end
 
-MyClass.execute("my class")
+MyClass.send_work("my class")
 # => Before processing
 # => Working with my class
 ```
@@ -105,7 +105,7 @@ MyClass.execute("my class")
 ### Serializers
 
 You can provide a Proc for the loader and/or the dumper keywords.
-The dumper will be used when calling `MyClass.execute(message)` receiving
+The dumper will be used when calling `MyClass.send_work(message)` receiving
 the `message` as argument. It should return a string. The loader will be
 used when the message is poped from the RabbitMQ queue.
 
@@ -124,7 +124,7 @@ class MyClass
   end
 end
 
-MyClass.execute([1, "foo"])
+MyClass.send_work([1, "foo"])
 # => Message is serialized and deserialized correctly
 # => one: 1, two: foo
 ```
@@ -143,7 +143,7 @@ class MyClass
   end
 end
 
-MyClass.execute([String, User.find(1)])
+MyClass.send_work([String, User.find(1)])
 # => Classes can be passed: String - Class
 # => Active record object can be passed too: <User#1 ...>
 ```

data/examples/serializer.rb

@@ -32,6 +32,6 @@ Example.new(__FILE__, SumWorker).run do
   array = Array.new(5) { 1 + rand(5) }
   print "Press enter to enqueue a random array..." ; gets
   puts "Sending #{array.inspect} to the #{SumWorker::Worker.queue_name} queue!"
-  SumWorker.execute(array)
+  SumWorker.send_work(array)
 end
 

data/lib/tennis/worker/deferable/action.rb

@@ -10,7 +10,7 @@ class Tennis::Worker::Deferable::Action
   def _create_methods!
     _methods.each do |method|
       self.define_singleton_method(method) do |*arguments|
-        @worker_class.execute([@receiver, method, arguments])
+        @worker_class.send_work([@receiver, method, arguments])
       end
     end
   end

data/lib/tennis/worker/generic.rb

@@ -37,7 +37,7 @@ module Tennis
           @_work ||= ->(_){ ack! }
         end
 
-        def execute(message)
+        def send_work(message)
           message = _apply_serializer(:dump, message)
           if Tennis.config.async
             publisher_opts = worker.queue_opts.select do |opt_name, _|

data/tennis-jobs.gemspec

@@ -4,7 +4,7 @@ $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
 
 Gem::Specification.new do |spec|
   spec.name          = "tennis-jobs"
-  spec.version       = "0.2.0"
+  spec.version       = "0.3.0"
   spec.authors       = ["Nicolas ZERMATI"]
   spec.email         = ["nicoolas25@gmail.com"]
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: tennis-jobs
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.3.0
 platform: ruby
 authors:
 - Nicolas ZERMATI