rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: rack-devel@googlegroups.com
Subject: Unicorn/Rainbows!/Zbatery "support" in rack.git...
Date: Thu, 14 Apr 2011 08:36:02 +0000	[thread overview]
Message-ID: <20110414083602.GA17769@dcvr.yhbt.net> (raw)

Hello, I'm the main support/helpdesk guy and project leader for
Unicorn/Rainbows!/Zbatery servers.   I believe
dff8e34f43c2897062d5b252406398ced2d360a8 to add handlers for these
servers is a bad change for everyone.

All three servers support Rack natively and were designed around the
Rack spec.  However the (sometimes minor) differences in using "rackup"
vs the shipped commands will cause confusion among both users and
developers trying to support them.

All three servers also rely on Unix signals for management, so their
names in the process table is also an important part of the user
experience.

Unlike typical web servers, Unicorn should never be directly exposed to
slow clients, but a user just trying it with "rackup" would never be
informed of that (especially since other servers like
Mongrel/Thin/WEBrick don't have this limitation).

Rainbows! and Zbatery are also completely worthless without a
configuration file, but "rackup" has no way of conveying that to the
user.  The user would just be left with an even worse version
of Unicorn.


I'm also under the impression that nobody uses Rainbows! or Zbatery,
yet, so I'd rather users' first impressions of those projects be
through the officially-supported and documented commands.

Thanks for reading, I hope you agree and revert the change.

-- 
Eric Wong

             reply	other threads:[~2011-04-14  8:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14  8:36 Eric Wong [this message]
2011-04-14 16:20 ` Unicorn/Rainbows!/Zbatery "support" in rack.git Aaron Patterson
2011-04-14 19:48   ` Eric Wong

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-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://groups.google.com/group/rack-devel

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

  git send-email \
    --in-reply-to=20110414083602.GA17769@dcvr.yhbt.net \
    --to=rack-devel@googlegroups.com \
    /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.
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).