Rainbows! Rack HTTP server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
To: rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
Subject: upcoming env['rack.input'] improvements
Date: Fri, 12 Nov 2010 16:29:17 -0800	[thread overview]
Message-ID: <20101113002917.GA8065@dcvr.yhbt.net> (raw)

Hello all,

The next versions of Unicorn and Rainbows! will support intentionally
violating the Rack 1.x spec and allowing non-rewindable input bodies
by setting:

  rewindable_input false

  (config directive name not finalized, feedback appreciated)

in the Unicorn/Rainbows! config file.  This will allow applications to
handle larger, streamed requests without worrying about disk/memory
usage at all.  For Rack 1.x conformance, this rewindable_input directive
true by default (but will probably be off with Rack 2.x).

Rainbows! will also support HTTP/1.1 keepalive for requests with a body,
but only if the body (and trailers) are fully consumed by the
application.

The implementation of Unicorn::TeeInput is also simplified and based on
Unicorn::StreamInput.  However there is one minor regression to TeeInput
made in the interest of simplicity that will not noticeable to most
users: calling env['rack.input'].rewind causes the entire request to be
buffered if any data has previously been read off env['rack.input'].


Evented concurrency options (e.g: :Rev and :EventMachine) continue to
buffer the entire body in the existing way, and are unaffected by any
of these changes (except keepalive will always function).

-- 
Eric Wong
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying


                 reply	other threads:[~2010-11-13  0:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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/rainbows/

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

  git send-email \
    --in-reply-to=20101113002917.GA8065@dcvr.yhbt.net \
    --to=normalperson-rmlxzr9ms24@public.gmane.org \
    --cc=rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.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 inbox:

	../../rainbows.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).