jruby-rack-worker 0.6-jruby → 0.7-jruby

Sign up to get free protection for your applications and to get access to all the features.
data/README.md CHANGED
@@ -1,12 +1,12 @@
1
- # JRuby Rack Worker
1
+ # JRuby-Rack-Worker
2
2
 
3
3
  Thread based workers on top of [jruby-rack](http://github.com/jruby/jruby-rack).
4
4
 
5
- With out of the box [JRuby](http://jruby.org) "adapters" for:
5
+ With out of the box thread-safe [JRuby](http://jruby.org) "adapters" for:
6
6
 
7
- * [Resque](http://github.com/defunkt/resque)
8
- * [Delayed::Job](http://github.com/collectiveidea/delayed_job)
9
- * [Navvy](http://github.com/jeffkreeftmeijer/navvy)
7
+ * [Resque](http://github.com/defunkt/resque) (>= 1.20.0)
8
+ * [Delayed::Job](http://github.com/collectiveidea/delayed_job) (~> 2.1, >= 3.0)
9
+ * [Navvy](http://github.com/jeffkreeftmeijer/navvy) (not-maintained)
10
10
 
11
11
  ... but one can easily write/adapt his own worker loop.
12
12
 
@@ -14,7 +14,7 @@ With out of the box [JRuby](http://jruby.org) "adapters" for:
14
14
  ## Motivation
15
15
 
16
16
  Ruby attempts to stay pretty close to UNIX and most popular workers have been
17
- modeled the spawn a background process way. [JRuby](http://jruby.org) brings
17
+ modeled the "spawn a background process" way. [JRuby](http://jruby.org) brings
18
18
  Java to the table, where "Young Java Knights" are thought to use threads
19
19
  whenever in a need to compute something parallel while serving requests.
20
20
 
@@ -23,7 +23,7 @@ proclaims - have long running jobs that consume a lot of memory they have troubl
23
23
  releasing (e.g. due C extensions) run a separate process for sure.
24
24
  But otherwise (after all C exts usually have a native Java alternative on JRuby)
25
25
  having predictable thread-safely written workers, one should be fine with
26
- running them concurrently as part of the application in a daemon thread.
26
+ running them concurrently as part of the application in a (daemon) thread.
27
27
 
28
28
  This does have the advantage of keeping the deployment simple and saving some
29
29
  precious memory (most notably with `threadsafe!` mode) that would have been
@@ -1,7 +1,7 @@
1
1
  module JRuby
2
2
  module Rack
3
3
  module Worker
4
- VERSION = '0.6'
4
+ VERSION = '0.7'
5
5
  end
6
6
  end
7
7
  end
metadata CHANGED
@@ -2,7 +2,7 @@
2
2
  name: jruby-rack-worker
3
3
  version: !ruby/object:Gem::Version
4
4
  prerelease:
5
- version: "0.6"
5
+ version: "0.7"
6
6
  platform: jruby
7
7
  authors:
8
8
  - Karol Bucek
@@ -10,7 +10,7 @@ autorequire:
10
10
  bindir: bin
11
11
  cert_chain: []
12
12
 
13
- date: 2012-10-11 00:00:00 Z
13
+ date: 2012-10-25 00:00:00 Z
14
14
  dependencies:
15
15
  - !ruby/object:Gem::Dependency
16
16
  name: jruby-rack
@@ -35,8 +35,8 @@ extra_rdoc_files: []
35
35
  files:
36
36
  - README.md
37
37
  - LICENSE
38
- - lib/jruby-rack-worker_0.6.jar
39
38
  - lib/jruby_rack_worker.rb
39
+ - lib/jruby-rack-worker_0.7.jar
40
40
  - lib/jruby/rack/worker.rb
41
41
  - lib/jruby/rack/worker/env.rb
42
42
  - lib/jruby/rack/worker/version.rb