diff options
author | Jeremy Evans <code@jeremyevans.net> | 2022-01-26 17:55:30 -0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-01-26 17:55:30 -0800 |
commit | 0f8bb0fa0fdbef5348d2c82c2f27f529f916a02b (patch) | |
tree | d46dfb12c429cdd11dc1dea00048a2556c971fe4 /SPEC.rdoc | |
parent | bc7f8d8a7fc73a15e98bfb86a231602fca255fda (diff) | |
download | rack-0f8bb0fa0fdbef5348d2c82c2f27f529f916a02b.tar.gz |
Remove `rack.multithread`/`rack.multiprocess`/`rack.run_once`
These variables generally come too late to be useful. Make `Rack::Lock`
always use a mutex.
Co-authored-by: Samuel Williams <samuel.williams@oriontransfer.co.nz>
Diffstat (limited to 'SPEC.rdoc')
-rw-r--r-- | SPEC.rdoc | 13 |
1 files changed, 0 insertions, 13 deletions
@@ -78,19 +78,6 @@ Rack-specific variables: request URL. <tt>rack.input</tt>:: See below, the input stream. <tt>rack.errors</tt>:: See below, the error stream. -<tt>rack.multithread</tt>:: true if the application object may be - simultaneously invoked by another thread - in the same process, false otherwise. -<tt>rack.multiprocess</tt>:: true if an equivalent application object - may be simultaneously invoked by another - process, false otherwise. -<tt>rack.run_once</tt>:: true if the server expects - (but does not guarantee!) that the - application will only be invoked this one - time during the life of its containing - process. Normally, this will only be true - for a server based on CGI - (or something similar). <tt>rack.hijack?</tt>:: present and true if the server supports connection hijacking. See below, hijacking. <tt>rack.hijack</tt>:: an object responding to #call that must be |