From: russell muetzelfeldt <russm-rubyforge@slofith.org>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Rainbows! or unicorn?
Date: Fri, 16 Sep 2011 22:38:59 +1000 [thread overview]
Message-ID: <D14F4D37-88B4-4B2F-B08B-0478C9EE4255@slofith.org> (raw)
In-Reply-To: <20110916111107.GA15421@dcvr.yhbt.net>
On 16/09/2011, at 9:11 PM, Eric Wong wrote:
> :ThreadSpawn + worker_connections=1 and the (default) :Base option are
> almost the same in Rainbows! if you don't want to worry about your app
> being thread-safe at all.
my reason for intending to run worker_connections=1 isn't avoiding threading issues, but to allow app reloads without leaving around old instances of the app in server processes that are handling a 2+ hour upload. I passed on Rainbows::Base just because of the "not intended for production use" comment in the docs.
> Rainbows! can (and does by default) limit upload sizes
> (client_max_body_size) for handling untrusted clients who may try to
> run you out of space.
ah, that's a good point. I'll be fronting through Pound for SSL, but having the server process limit upload size would be worthwhile.
> Since performance/scalability isn't your concern, it depends on whether
> you trust your clients to not upload until you run out of disk space.
I trust them to not do that on purpose, but that doesn't mean a lot. :/
cheers
Russell
-----
Russell Muetzelfeldt <russm@slofith.org>
Mundus vult decipi, ergo decipiatur.
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
next prev parent reply other threads:[~2011-09-16 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 10:19 Rainbows! or unicorn? russell muetzelfeldt
2011-09-16 11:11 ` Eric Wong
2011-09-16 12:38 ` russell muetzelfeldt [this message]
2011-09-16 17:00 ` 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=D14F4D37-88B4-4B2F-B08B-0478C9EE4255@slofith.org \
--to=russm-rubyforge@slofith.org \
--cc=mongrel-unicorn@rubyforge.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).