From: James Tucker <jftucker@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: ctrl-c not working in Rack::Handler::WEBrick
Date: Thu, 20 Jan 2011 12:35:28 -0800 [thread overview]
Message-ID: <4693FBB8-2F15-424A-805E-72E4775B8994@gmail.com> (raw)
In-Reply-To: <30804305.1700.1295469219531.JavaMail.geo-discussion-forums@vbxq13>
[-- Attachment #1: Type: text/plain, Size: 380 bytes --]
On Jan 19, 2011, at 12:33 PM, Alex Chaffee wrote:
> So to be clear (and to educate others who, like me, found this page after googling "rack webrick handler interrupt") -- when you want to invoke a Rack server programmatically, instead of
> Rack::Handler.default.run(app, options)
> ...the correct behavior is to use
>
> Rack::Server.start(options)
> ...right?
Yes.
[-- Attachment #2: Type: text/html, Size: 5451 bytes --]
next prev parent reply other threads:[~2011-01-20 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 2:48 ctrl-c not working in Rack::Handler::WEBrick Stephen Bannasch
2010-07-12 15:44 ` James Tucker
2011-01-19 20:33 ` Alex Chaffee
2011-01-20 20:35 ` James Tucker [this message]
2011-01-21 18:56 ` Alex Chaffee
2011-01-21 19:47 ` James Tucker
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=4693FBB8-2F15-424A-805E-72E4775B8994@gmail.com \
--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).