From: Eric Wong <e@80x24.org>
To: unicorn-public@bogomips.org
Cc: Adam Duke <adamduke@twitter.com>,
Aaron Patterson <tenderlove@ruby-lang.org>
Subject: Re: [PATCH] limit rack version for ruby compatibility
Date: Wed, 27 Jan 2016 00:47:35 +0000 [thread overview]
Message-ID: <20160127004735.GA16295@dcvr.yhbt.net> (raw)
In-Reply-To: <20160121201255.GA6186@dcvr.yhbt.net>
Eric Wong <e@80x24.org> wrote:
> I prefer we drop the rack dependency entirely. We don't use rack
> for much. This seems doable, (totally untested) patch below:
(removed rack-devel from Cc:)
Tested and pushed to unicorn.git master with minor changes
as commit 3d69a6f064078eeb28c1819725d3715ce6905374
* use nil instead of '[]' for empty splat to reduce garbage
* rack is a development dependency, not removed as a dep entirely
http://bogomips.org/unicorn.git/patch?id=3d69a6f064078
Subject: rack is optional at runtime, required for dev
We do not want to pull in a newer or older version of rack depending
on an the application running under it requires. Furthermore, it
has always been possible to use unicorn without any middleware at
all.
Without rack, we'll be missing descriptive status text in the first
response line, but any valid HTTP/1.x parser should be able to
handle it properly.
ref:
http://bogomips.org/unicorn-public/20160121201255.GA6186@dcvr.yhbt.net/t/#u
Thanks-to: Adam Duke <adam.v.duke@gmail.com>
Thanks-to: Aaron Patterson <tenderlove@ruby-lang.org>
prev parent reply other threads:[~2016-01-27 0:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 18:34 [PATCH] limit rack version for ruby compatibility Adam Duke
2016-01-08 19:18 ` Eric Wong
2016-01-08 21:50 ` Aaron Patterson
2016-01-08 21:56 ` Aaron Patterson
2016-01-08 22:13 ` Adam Duke
2016-01-08 22:17 ` Aaron Patterson
2016-01-08 22:37 ` Eric Wong
2016-01-08 23:19 ` Aaron Patterson
2016-01-21 17:12 ` Adam Duke
2016-01-21 20:12 ` Eric Wong
2016-01-21 22:09 ` Aaron Patterson
2016-01-27 0:47 ` 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=20160127004735.GA16295@dcvr.yhbt.net \
--to=e@80x24.org \
--cc=adamduke@twitter.com \
--cc=tenderlove@ruby-lang.org \
--cc=unicorn-public@bogomips.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).