From: James Tucker <jftucker@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: rack 1.2.2 release => Rack::Server.new(:app => app).start
Date: Sun, 26 Sep 2010 16:18:07 -0300 [thread overview]
Message-ID: <61CCDA29-8D57-4D86-AD20-D0C6F19498F2@gmail.com> (raw)
In-Reply-To: <c89307bc-2e73-4b07-92a1-6380ded20996@z28g2000yqh.googlegroups.com>
On 25 Sep 2010, at 13:45, trans wrote:
>
>
> On Aug 28, 2:41 pm, Jeremy Hinegardner <jer...@hinegardner.org> wrote:
>> Hi all,
>>
>> I too would like to use Rack::Server by passing in an app.
>> For the moment I'm working around it with:
>>
>> server = ::Rack::Server.new( options )
>> server.instance_variable_set('@app', options[:app] )
>> server.start
>
> And how do you build `app` ?
It's anything that response to #call with an env and returns a rack response style tuple [status, headers, body].
prev parent reply other threads:[~2010-09-26 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 16:24 rack 1.2.2 release => Rack::Server.new(:app => app).start Stephen Bannasch
2010-08-28 18:41 ` Jeremy Hinegardner
2010-09-25 16:45 ` trans
2010-09-26 19:18 ` James Tucker [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=61CCDA29-8D57-4D86-AD20-D0C6F19498F2@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).