Rainbows! Rack HTTP server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: rainbows-public@bogomips.org
Cc: ruby-talk@ruby-lang.org
Subject: Re: [ANN] Rainbows! 4.7.0 - Rack HTTP server for the sleepy
Date: Tue, 20 Oct 2015 09:59:34 +0000	[thread overview]
Message-ID: <20151020095934.GA19114@dcvr.yhbt.net> (raw)
In-Reply-To: <20151019-rainbows-4.7.0-rele@sed>

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 :>

      reply	other threads:[~2015-10-20  9:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19 21:28 [ANN] Rainbows! 4.7.0 - Rack HTTP server for the sleepy Eric Wong
2015-10-20  9:59 ` Eric Wong [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://yhbt.net/rainbows/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151020095934.GA19114@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=rainbows-public@bogomips.org \
    --cc=ruby-talk@ruby-lang.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).