[ANN] Rainbows! 4.7.0 - Rack HTTP server for the sleepy

[ANN] Rainbows! 4.7.0 - Rack HTTP server for the sleepy

[Eric Wong]

Rainbows! is an HTTP server for sleepy Rack applications.
Use of Rainbows! for new projects is not recommended,
try other servers instead.

Changes since 4.6.2:

    Rainbows! 4.7.0 - updates for ruby 2.3.0dev

    This release includes fixes for upcoming changes in Ruby 2.3.0
    (due December 2015).  Use of Rainbows! for new projects is not
    recommended, try other servers instead.

    * update dependencies for Ruby 2.2.0dev
    * switch docs + website to olddoc
    * gemspec: fix bad reference to rdoc_options
    * README: reference yahns
    * build: fix quoting issue with double parens
    * response: avoid unnecessary args to IO.copy_stream
    * t/close-has-env.ru: ensure close is idempotent
    * sync_close: This fix breakage from Ruby-trunk r50118
    * t/t0044-autopush.sh: remove test
    * t/test_isolate.rb: updates for various gem versions
    * response: convert source arg to path before IO.copy_stream
    * speed up QUIT for users of the unicorn worker_loop
    * gemspec: use SPDX-compatible license for GPL-2.0+

* http://rainbows.bogomips.org/
* rainbows-public@bogomips.org
* http://bogomips.org/rainbows-public/
* git clone git://bogomips.org/rainbows.git
* http://rainbows.bogomips.org/NEWS.atom.xml

Re: [ANN] Rainbows! 4.7.0 - Rack HTTP server for the sleepy

[Eric Wong]

Eric Wong <normalperson@yhbt.net> wrote:
> Rainbows! is an HTTP server for sleepy Rack applications.
> Use of Rainbows! for new projects is not recommended,
> try other servers instead.

Just to clarify (based on a personal reply I got):

Rainbows! remains supported for existing users, I just don't want to
confuse new people with dozens of options as far as concurrency models
are concerned.

I don't like most of the concurrency options in Rainbows!  My
favorite is suboptimally implemented for compatibility with other
models.  It would be against the spirit of the project to publically
endorse/favor any.

Also, the "timeout" option somewhat made sense for unicorn to tolerate
buggy apps, but is totally insane for using with Rainbows! because you
can nuke thousands of clients, not just one.

yahns <http://yahns.yhbt.net/README> suits my needs fine.  But it's not
a drop-in-replacement because it has absolutely zero-tolerance of bugs
anywhere in the stack, and not just your app code.  yahns is probably
more sensitive to bugs in the Linux/FreeBSD kernels than any other
server (even those outside of Ruby).

unicorn happily tolerates and encourages buggy applications to exist.
Rainbows! mistakenly tried to inherit that tolerance of buggy apps
from unicorn.  yahns will burn down your datacenter if there's a bug :>