From: Hongli Lai <hongli@phusion.nl>
To: rack-devel@googlegroups.com
Cc: ruby-talk@ruby-lang.org, rack-core@googlegroups.com
Subject: Re: [SEC][ANN] Rack 1.5.0, a modular Ruby webserver interface
Date: Tue, 22 Jan 2013 10:14:33 -0800 (PST) [thread overview]
Message-ID: <03a7f2cd-bf04-43cd-a6ba-a27e6a04583f@googlegroups.com> (raw)
In-Reply-To: <50fe43c2.68dc440a.126d.ffffe987@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 176 bytes --]
We've also implemented the socket hijacking API in the upcoming Phusion
Passenger
4: https://github.com/FooBarWidget/passenger/commit/c5b5b2e76034f7c7010c46aefc08967240eda122
[-- Attachment #2: Type: text/html, Size: 179 bytes --]
prev parent reply other threads:[~2013-01-22 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 7:46 [SEC][ANN] Rack 1.5.0, a modular Ruby webserver interface jftucker
2013-01-22 7:46 ` raggi
2013-01-22 10:08 ` Eric Wong
2013-01-23 0:27 ` Eric Wong
2013-01-23 22:40 ` Hongli Lai
2013-01-26 19:11 ` James Tucker
2013-01-22 18:14 ` Hongli Lai [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-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=03a7f2cd-bf04-43cd-a6ba-a27e6a04583f@googlegroups.com \
--to=rack-devel@googlegroups.com \
--cc=rack-core@googlegroups.com \
--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.
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).