From: Eric Wong <normalperson@yhbt.net>
To: rack-devel@googlegroups.com
Subject: Re: Rack 2 (rack-devel@googlegroups.com)
Date: Sat, 6 Jul 2013 03:32:56 +0000 [thread overview]
Message-ID: <20130706033256.GB5489@dcvr.yhbt.net> (raw)
In-Reply-To: <e89a8ff256f4537f9104e0b85eb4@google.com>
"James Tucker (Google Drive)" <jftucker@gmail.com> wrote:
> This is a straw man start of the Rack 2 design doc / todo list.
I think small, gradual improvements are the way to go.
That said, I think everything on the list seams reasonable.
Am I correct the input body will remain IO-like (and not
callback-driven, so evented servers can avoid buffering the body?)
Likewise for streaming responses via response_body.each
Those would be the only major API/design change/incompatibilities I can
think of, but perhaps theyd'd break too much existing code to be called
Rack.
--
---
You received this message because you are subscribed to the Google Groups "Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
next prev parent reply other threads:[~2013-07-06 3:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 23:59 Rack 2 (rack-devel@googlegroups.com) James Tucker (Google Drive)
2013-07-05 0:32 ` Oscar Del Ben
2013-07-06 3:22 ` Eric Wong
2013-07-06 3:32 ` Eric Wong [this message]
2013-07-10 2:18 ` James Tucker
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=20130706033256.GB5489@dcvr.yhbt.net \
--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).