From: Eric Wong <e@80x24.org>
To: unicorn-public@bogomips.org
Cc: e@80x24.org
Subject: [PATCH 0/2] no avoiding rack.hijack anymore
Date: Sat, 16 May 2015 21:30:23 +0000 [thread overview]
Message-ID: <1431811825-20664-1-git-send-email-e@80x24.org> (raw)
I'm not sure if it makes sense to use rack.hijack with a prefork server
like unicorn which only works behind nginx, but maybe somebody does...
Eric Wong (2):
http_request: support rack.hijack by default
avoid extra allocation for hijack proc creation
lib/unicorn/http_request.rb | 40 ++++++++++++++++------------------------
1 file changed, 16 insertions(+), 24 deletions(-)
next reply other threads:[~2015-05-16 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-16 21:30 Eric Wong [this message]
2015-05-16 21:30 ` [PATCH 1/2] http_request: support rack.hijack by default Eric Wong
2015-05-19 20:01 ` [PATCH] http_response: avoid special-casing for Rack < 1.5 Eric Wong
2015-05-16 21:30 ` [PATCH 2/2] avoid extra allocation for hijack proc creation 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-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=1431811825-20664-1-git-send-email-e@80x24.org \
--to=e@80x24.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).