From: Augusto Becciu <augusto@jadedpixel.com>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: [ANN] unicorn 1.0.0 - yes, this is a real project
Date: Thu, 17 Jun 2010 22:47:35 -0300 [thread overview]
Message-ID: <AANLkTil-pO4my3h6POO1XGd2nghbBwE0A1BtqClJNYUR@mail.gmail.com> (raw)
In-Reply-To: <20100617100825.GA17552@dcvr.yhbt.net>
Wow, awesome. Huge congrats Eric!
On Thu, Jun 17, 2010 at 7:08 AM, Eric Wong <normalperson@yhbt.net> wrote:
> Unicorn is an HTTP server for Rack applications designed to only serve
> fast clients on low-latency, high-bandwidth connections and take
> advantage of features in Unix/Unix-like kernels. Slow clients should
> only be served by placing a reverse proxy capable of fully buffering
> both the the request and response in between Unicorn and slow clients.
>
> * http://unicorn.bogomips.org/
> * mongrel-unicorn@rubyforge.org
> * git://git.bogomips.org/unicorn.git
>
> Changes:
>
> There are only minor changes since 0.991.0.
>
> For users clinging onto the past, MRI 1.8.6 support has been
> restored. Users are strongly encouraged to upgrade to the
> latest 1.8.7, REE or 1.9.1.
>
> For users looking towards the future, the core test suite and
> the Rails 3 (beta) integration tests pass entirely under 1.9.2
> preview3. As of the latest rubinius.git[1], Rubinius support is
> nearly complete as well.
>
> Under Rubinius, signals may corrupt responses as they're being
> written to the socket, but that should be fixable transparently
> to us[4]. Support for the hardly used, hardly documented[2]
> embedded command-line switches in rackup config (.ru) files is
> is also broken under Rubinius.
>
> The recently-released Rack 1.2.1 introduced no compatiblity
> issues[3] in core Unicorn. We remain compatible with all Rack
> releases starting with 0.9.1 (and possibly before).
>
> [1] tested with Rubinius upstream commit
> cf4a5a759234faa3f7d8a92d68fa89d8c5048f72
> [2] lets avoid the Dueling Banjos effect here :x
> [3] actually, Rack 1.2.1 is broken under 1.8.6.
> [4] http://github.com/evanphx/rubinius/issues/373
>
>
> The Future:
>
> * Bug/compatibility fixes as needed, of course!
> * Scalability for hardware that may be common in 5-10 years
> * Rainbows! LOTS of Rainbows!
>
> Thanks for reading!
>
> --
> Eric Wong
> _______________________________________________
> Unicorn mailing list - mongrel-unicorn@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-unicorn
> Do not quote signatures (like this one) or top post when replying
>
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
prev parent reply other threads:[~2010-06-18 1:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 10:08 [ANN] unicorn 1.0.0 - yes, this is a real project Eric Wong
2010-06-17 10:17 ` Wincent Colaiuta
2010-06-17 15:31 ` David Palm
2010-06-18 1:47 ` Augusto Becciu [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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTil-pO4my3h6POO1XGd2nghbBwE0A1BtqClJNYUR@mail.gmail.com \
--to=augusto@jadedpixel.com \
--cc=mongrel-unicorn@rubyforge.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/unicorn.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).