From: Eric Wong <normalperson@yhbt.net>
To: ruby-talk@ruby-lang.org (ruby-talk ML) ,rainbows-talk@rubyforge.org
Subject: [ANN] Zbatery - Rack HTTP server without a fork stuck in it
Date: Thu, 10 Dec 2009 18:19:22 +0900 [thread overview]
Message-ID: <20091210091919.GB24828@dcvr.yhbt.net> (raw)
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.
Zbatery will still exploit certain features of Unix for transparent
upgrades, log reopening, and graceful stops, but does not rely on them
for basic functionality.
* http://zbatery.bogomip.org/
* rainbows-talk@rubyforge.org
* git://git.bogomips.org/zbatery.git
== Features
* Designed for {Rack}[http://rack.rubyforge.org/], the standard for
modern Ruby HTTP applications.
* Configuration files are compatible with Rainbows!, a superset
of the Unicorn
{DSL}[http://unicorn.bogomips.org/Unicorn/Configurator.html].
* Inherits all features and concurrency models Rainbows! supports
(and ever will support): http://rainbows.rubyforge.org/Summary.html
* -Untested- Works under operating systems that don't support signals,
pipe and fork(). Unicorn 0.95.2+ has rake-compiler support, so
compiling the HTTP parser should be easier at least.
* -Untested- HTML 5 Web Sockets support
This project may be temporary and may eventually have its name encoded
with uncrackable ROT13 encryption leaving you with no way to upgrade.
--
Eric Wong
reply other threads:[~2009-12-10 9:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=20091210091919.GB24828@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=rainbows-talk@rubyforge.org \
--cc=ruby-talk@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://yhbt.net/rainbows.git/
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).