From: Joshua Peek <josh@joshpeek.com>
To: rack-devel@googlegroups.com
Subject: Re: Rack::Server patch
Date: Fri, 20 Nov 2009 18:10:05 -0800 [thread overview]
Message-ID: <1c5622660911201810v4cd86215ve20fb6a09864afe5@mail.gmail.com> (raw)
In-Reply-To: <245fb4700911201652s63cafa2fg160820c7dce479ec@mail.gmail.com>
+1 Looks good.
My only suggestion would be to keep the old pid/daemonize behavior. So
don't set a default pid file and only set one if its provided.
On Fri, Nov 20, 2009 at 4:52 PM, Yehuda Katz <wycats@gmail.com> wrote:
> Patches attached.
> [1] tests_patch.diff -- Adds tests for the functionality of rackup
> [2] rack_server_patch.diff -- Moves Rack::Server into a separate object
> Yehuda Katz
> Developer | Engine Yard
> (ph) 718.877.1325
>
>
> 2009/11/20 Yehuda Katz <wycats@gmail.com>
>>
>> Hey guys,
>> Carl and I spent a couple of day refactoring the code in bin/rackup into
>> Rack::Server. The main motivation for this was to enable Rails to ditch our
>> code in script/server and simply inherit from the requisite Rack code. I
>> think the code improvement speaks for itself. In the process of this work,
>> we also moved a few things out of Rackup into more usable locations, like
>> Rack::Handler.default (to get the handler that Rack will use if none is
>> specified) and Rack::Builder.parse_file (which we currently duplicate in
>> ActionDispatch).
>> You can check out the changes at github.com/carllerche/rack, and I have
>> also attached a patch. In addition to converting the rackup binary to a
>> class, we also wrote tests for each function of rackup, to be sure we
>> wouldn't break anything in the refactor. As a result, this patch now has
>> tests for rackup!
>> Yehuda Katz
>> Developer | Engine Yard
>> (ph) 718.877.1325
>
>
--
Joshua Peek
next prev parent reply other threads:[~2009-11-21 2:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 0:42 Rack::Server patch Yehuda Katz
2009-11-21 0:46 ` Yehuda Katz
2009-11-21 0:52 ` Yehuda Katz
2009-11-21 2:10 ` Joshua Peek [this message]
2009-11-21 10:17 ` Christian Neukirchen
2009-11-21 10:18 ` Christian Neukirchen
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=1c5622660911201810v4cd86215ve20fb6a09864afe5@mail.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).