unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: ruby-talk@ruby-lang.org
Cc: mongrel-unicorn@rubyforge.org
Subject: Re: unicorn 0.8.2 and 0.9.1
Date: Fri, 10 Jul 2009 12:52:20 -0700	[thread overview]
Message-ID: <20090710195220.GA13208@dcvr.yhbt.net> (raw)
In-Reply-To: <3670459b7de642ba5d5a0ce074534b83@ruby-forum.com>

Roger Pack <rogerpack2005@gmail.com> wrote:
> Eric Wong wrote:
> > Unicorn is a Rack HTTP server for Unix, fast clients and nothing else
> 
> So who exactly would benefit most from this library?  What is the target 
> audience?  Just wondering more background on it.

The target audience is people deploying/maintaining/managing HTTP apps
that only clients within their LAN are expected/allowed to hit.  Of
course, with a decent reverse proxy in front, all traffic from the
reverse proxy can be considered internal and fast (unless your LAN is
horrible).

Clients don't have to be on a Unix-like OS, of course.

It's also a testing ground for features that may make it into Mongrel 2
(assuming portability requirements are met).  Unicorn gives us more
freedom to exploit features unique to Unix-like systems (and maybe even
(optionally) Linux 2.6+ in the future).

Fwiw, I've known about (and implemented similar (but meaner :)) things
like the recently-disclosed Slowloris for several years now.  That's why
we refuse to support Unicorn talking directly to the Internet at large.

There's also some philosophy and design notes here that describe why we
did some of the things we did:

  http://unicorn.bogomips.org/PHILOSOPHY.html
  http://unicorn.bogomips.org/DESIGN.html

-- 
Eric Wong

      parent reply	other threads:[~2009-07-10 19:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09  9:09 [ANN] unicorn 0.8.2 and 0.9.1 Eric Wong
     [not found] ` <3670459b7de642ba5d5a0ce074534b83@ruby-forum.com>
2009-07-10 19:52   ` 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:
  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=20090710195220.GA13208@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=mongrel-unicorn@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/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).