yahns Ruby server user/dev discussion
 help / color / mirror / code / Atom feed
From: "Lin Jen-Shin (godfat)" <godfat@godfat.org>
To: Eric Wong <e@80x24.org>
Cc: yahns-public@yhbt.net
Subject: Re: [RFC] remove documentation for client_*_buffer_size knobs
Date: Tue, 17 Mar 2015 06:40:59 +0800	[thread overview]
Message-ID: <CAA2_N1t_UJZO9Vu9vx3NxysCx+okip8_pM+NpwhHrExM+f1e+Q@mail.gmail.com> (raw)
In-Reply-To: <20150316211532.GA17889@dcvr.yhbt.net>

On Tue, Mar 17, 2015 at 5:15 AM, Eric Wong <e@80x24.org> wrote:
[...]
> In the future, we may remove these options entirely.  For now,
> having too much documentation and tuning options may confuse new
> users and minimize the importance/visibility of other options,
> so remove documentation for this.
>
> I'm not convinced user-space buffer size tuning has a place in
> an application server written in a high-level language.  Heck,
> many servers written in C do not have this.

Personally I do like various options even if I won't touch them,
since maybe I'll on some day. We could put more advanced
options in advanced configuration page to avoid confusion.
Or a warning like "Don't touch them unless you really know
what you're doing" should be good (scary) enough.

However, I don't know if it makes sense to configure
client_header_buffer_size and client_max_body_size.
(nginx has them, I think?) If not, I guess it's really fine to
remove them, and we're free to change them or stop
providing those options in the future. That's also good, I guess.

  reply	other threads:[~2015-03-16 22:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 21:15 [RFC] remove documentation for client_*_buffer_size knobs Eric Wong
2015-03-16 22:40 ` Lin Jen-Shin (godfat) [this message]
2015-03-18 20: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/yahns/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA2_N1t_UJZO9Vu9vx3NxysCx+okip8_pM+NpwhHrExM+f1e+Q@mail.gmail.com \
    --to=godfat@godfat.org \
    --cc=e@80x24.org \
    --cc=yahns-public@yhbt.net \
    /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/yahns.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).