Rainbows! 4.6.2 - Rack HTTP server for the sleepy

Rainbows! is an HTTP server for sleepy Rack applications. It is based
on
Unicorn, but designed to handle applications that expect long
request/response times and/or slow clients.

Changes: Rainbows! 4.6.2 - see you on the other side

This release updates documentation to reflect the migration of the
mailing list to a new public-inbox[1] instance. This is necessary
due to the impending RubyForge shutdown on May 15, 2014.

The public-inbox address is: [email protected]
(no subscription required, plain text only)
ssoma[2] git archives: git://bogomips.org/rainbows-public
browser-friendly archives: http://bogomips.org/rainbows-public/

As evidenced by our git history, Rainbows! development has stagnated
over the years. Rainbows! was designed to be an unopinionated
exploration into various concurrency options offered in the Ruby
ecosystem.

In recent years, I have come to favor the one-shot-based,
worst-of-all-worlds design of yahns: http://yahns.yhbt.net/README
Without the exploration from Rainbows!, yahns may not exist today.

Disclaimer: Rainbows! has always been intolerant of buggy/broken code in
libraries and apps. yahns is even less tolerant of buggy/broken code,
as the SIGKILL-based timeout mechanism inherited unicorn is completely
gone. On the other hand, yahns has reasonable defaults so you do not
have to read documentation to configure it.

[1] policy: http://public-inbox.org/ - git://80x24.org/public-inbox
an “archives first” approach to mailing lists
[2] mechanism: http://ssoma.public-inbox.org/ - git://80x24.org/ssoma
some sort of mail archiver (using git)

Zbatery is an HTTP server for Rack applications on systems that either
do not support fork(), or have no memory (nor need) to run the
master/worker model. It is based on Rainbows! (which is based on
Unicorn (which is based on Mongrel)) and inherits parts of each.
Zbatery supports your choice of all the thread/fiber/event/actor-based
concurrency models and Rack middleware that Rainbows! supports (or will
ever support) in a single process.

Changes:

Lots of updates for deprecated broken stuff, and we have a good
version number to go with it :wink:

See the corresponding Rainbows! release for more details:
http://bogomips.org/rainbows-public/m/[email protected]

One notable new feature is the addition of the
–no-default-middleware option which I forgot about and should’ve
released last year when Rainbows! got it :x

Eric W. (6):
Rakefile: s/freshmeat.net/freecode.com/
Rakefile: kill raa_update task
rubyforge death updates
update license to GPLv2+
warn about premature grandparent death on daemonization
update for Rainbows! compatibility

Lin Jen-Shin (1):
Add -N or --no-default-middleware option.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs