jruby-rack 1.1.7 → 1.1.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/History.txt +34 -0
- data/README.md +24 -13
- data/lib/{jruby-rack-1.1.7.jar → jruby-rack-1.1.9.jar} +0 -0
- data/lib/jruby/rack/version.rb +1 -1
- metadata +3 -3
data/History.txt
CHANGED
@@ -1,3 +1,37 @@
|
|
1
|
+
== 1.1.9 (19/08/12)
|
2
|
+
|
3
|
+
- rack env regression fix when used with rack-cache, introduced in 1.1.8 (#116)
|
4
|
+
request.env should work correctly when (duped and) frozen
|
5
|
+
|
6
|
+
== 1.1.8 (17/08/12)
|
7
|
+
|
8
|
+
- introduced ServletEnv for cases when it's desirable to fully use the servlet
|
9
|
+
environment to create the rack env (and not let Rack::Request parse params
|
10
|
+
but rely on the parameters already parsed and available from the servlet
|
11
|
+
request #110). this is an experimental feature that might change in the
|
12
|
+
future and requires setting 'jruby.rack.handler.env' param to 'servlet' !
|
13
|
+
- separated out Env (LazyEnv) into a separate file :
|
14
|
+
- Env got refactored into DefaultEnv (with lazyness built-in)
|
15
|
+
- LazyEnv got removed as it is not longer necessary
|
16
|
+
- Rack::Handler::Servlet.env sets the used env conversion class
|
17
|
+
- introduce a generic getNumberProperty on RackConfig
|
18
|
+
- introduce a base RackException and add a custom AcquireTimeoutException for
|
19
|
+
pool timeouts (related to jruby.runtime.acquire.timeout parameter)
|
20
|
+
- RackInitializationException changed to unchecked as it inherits from
|
21
|
+
RackException now
|
22
|
+
- PoolingRackApplication (and related) polishing :
|
23
|
+
- avoid creating a new application from getApplication when a permit is
|
24
|
+
granted but pool is empty
|
25
|
+
- support to wait till pool becomes ready by default otherwise wait until
|
26
|
+
initial application objects are present in the pool before returning
|
27
|
+
(controlled with the jruby.runtime.init.wait accepting true/false/integer)
|
28
|
+
- edge case handling where (in case were set to not wait for initialization)
|
29
|
+
we should wait for an initializer thread to put an application into the pool
|
30
|
+
- allow acquire timeout (jruby.runtime.acquire.timeout param) to be specified
|
31
|
+
as a decimal number for finer control and decreased the timeout default
|
32
|
+
from 30s to 10s (although seems still too high for a default)
|
33
|
+
- jruby runtime pooling for plain Rack applications (not just Rails)
|
34
|
+
|
1
35
|
== 1.1.7 (21/06/12)
|
2
36
|
|
3
37
|
- support for delegating logs to java.util.logging (jruby.rack.logging: JUL)
|
data/README.md
CHANGED
@@ -144,8 +144,11 @@ Several aspects of Rails are automatically set up for you.
|
|
144
144
|
## JRuby Runtime Management
|
145
145
|
|
146
146
|
JRuby runtime management and pooling is done automatically by the framework.
|
147
|
-
In the case of Rails, runtimes are pooled
|
148
|
-
|
147
|
+
In the case of Rails, runtimes are pooled by default (the default will most
|
148
|
+
likely change with the adoption of Rails 4.0). For other Rack applications a
|
149
|
+
single shared runtime is created and shared for every request by default (as of
|
150
|
+
**1.1.8** if *jruby.min.runtimes*/*jruby.max.runtimes* values are specified
|
151
|
+
pooling is supported as well).
|
149
152
|
|
150
153
|
## JRuby-Rack Configuration
|
151
154
|
|
@@ -155,19 +158,8 @@ as context init parameters in web.xml or as VM-wide system properties.
|
|
155
158
|
- `rackup`: Rackup script for configuring how the Rack application is mounted.
|
156
159
|
Required for Rack-based applications other than Rails. Can be omitted if a
|
157
160
|
*config.ru* is included in the application root.
|
158
|
-
- `jruby.min.runtimes`: For non-threadsafe Rails applications using a runtime
|
159
|
-
pool, specify an integer minimum number of runtimes to hold in the pool.
|
160
|
-
- `jruby.max.runtimes`: For non-threadsafe Rails applications, an integer
|
161
|
-
maximum number of runtimes to keep in the pool.
|
162
|
-
- `jruby.init.serial`: When using runtime pooling, indicate that the runtime
|
163
|
-
pool should be created serially in the foreground rather than spawning
|
164
|
-
background threads. For environments where creating threads is not permitted.
|
165
|
-
- `jruby.compat.version`: Set to "1.8" or "1.9" to make JRuby run a specific
|
166
|
-
version of Ruby.
|
167
161
|
- `public.root`: Relative path to the location of your application's static
|
168
162
|
assets. Defaults to */*.
|
169
|
-
- `gem.path`: Relative path to the bundled gem repository. Defaults to
|
170
|
-
*/WEB-INF/gems*.
|
171
163
|
- `rails.root`: Root path to the location of the Rails application files.
|
172
164
|
Defaults to */WEB-INF*.
|
173
165
|
- `rails.env`: Specify the Rails environment to run. Defaults to 'production'.
|
@@ -175,6 +167,25 @@ as context init parameters in web.xml or as VM-wide system properties.
|
|
175
167
|
`ActionController::Base.relative_url_root` after the context path. Useful
|
176
168
|
for running a rails app from the same war as an existing app, under a
|
177
169
|
sub-path of the main servlet context root.
|
170
|
+
- `gem.path`: Relative path to the bundled gem repository. Defaults to
|
171
|
+
*/WEB-INF/gems*.
|
172
|
+
- `jruby.compat.version`: Set to "1.8" or "1.9" to make JRuby run a specific
|
173
|
+
version of Ruby (same as the --1.8 / --1.9 command line flags).
|
174
|
+
- `jruby.min.runtimes`: For non-threadsafe Rails applications using a runtime
|
175
|
+
pool, specify an integer minimum number of runtimes to hold in the pool.
|
176
|
+
- `jruby.max.runtimes`: For non-threadsafe Rails applications, an integer
|
177
|
+
maximum number of runtimes to keep in the pool.
|
178
|
+
- `jruby.runtime.init.threads`: How many threads to use for initializing
|
179
|
+
application runtimes when pooling is used (default is 4).
|
180
|
+
It does not make sense to set this value higher than `jruby.max.runtimes`.
|
181
|
+
- `jruby.runtime.init.serial`: When using runtime pooling, this flag indicates
|
182
|
+
that the pool should be created serially in the foreground rather than
|
183
|
+
spawning (background) threads, it's by default off (set to false).
|
184
|
+
For environments where creating threads is not permitted.
|
185
|
+
- `jruby.runtime.acquire.timeout`: The timeout in seconds (default 10) to use
|
186
|
+
when acquiring a runtime from the pool (while a pool maximum is set), an
|
187
|
+
exception will be thrown if a runtime can not be acquired within this time (
|
188
|
+
accepts decimal values for fine tuning e.g. 1.25).
|
178
189
|
- `jruby.rack.logging`: Specify the logging device to use. Defaults to
|
179
190
|
`servlet_context`. See below.
|
180
191
|
- `jruby.rack.ignore.env`: Clears out the `ENV` hash in each runtime to insulate
|
Binary file
|
data/lib/jruby/rack/version.rb
CHANGED
metadata
CHANGED
@@ -2,7 +2,7 @@
|
|
2
2
|
name: jruby-rack
|
3
3
|
version: !ruby/object:Gem::Version
|
4
4
|
prerelease:
|
5
|
-
version: 1.1.
|
5
|
+
version: 1.1.9
|
6
6
|
platform: ruby
|
7
7
|
authors:
|
8
8
|
- Nick Sieger
|
@@ -10,7 +10,7 @@ autorequire:
|
|
10
10
|
bindir: bin
|
11
11
|
cert_chain: []
|
12
12
|
|
13
|
-
date: 2012-
|
13
|
+
date: 2012-08-19 00:00:00 Z
|
14
14
|
dependencies: []
|
15
15
|
|
16
16
|
description: JRuby-Rack is a combined Java and Ruby library that adapts the Java Servlet API to Rack. For JRuby only.
|
@@ -26,8 +26,8 @@ files:
|
|
26
26
|
- README.md
|
27
27
|
- LICENSE.txt
|
28
28
|
- History.txt
|
29
|
+
- lib/jruby-rack-1.1.9.jar
|
29
30
|
- lib/jruby-rack.rb
|
30
|
-
- lib/jruby-rack-1.1.7.jar
|
31
31
|
- lib/jruby/rack/version.rb
|
32
32
|
homepage: http://jruby.org
|
33
33
|
licenses: []
|