rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: James Tucker <jftucker@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: Rack 2 (rack-devel@googlegroups.com)
Date: Tue, 9 Jul 2013 19:18:44 -0700	[thread overview]
Message-ID: <CABGa_T8yN0-TRA46UR9AcbrK+W0ZPKoaOERqjJrQCU-Tc=UP7g@mail.gmail.com> (raw)
In-Reply-To: <20130706033256.GB5489@dcvr.yhbt.net>

[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]

On Fri, Jul 5, 2013 at 8:32 PM, Eric Wong <normalperson@yhbt.net> wrote:

> "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
>

On input, almost certainly.

I'm quite unhappy with the streaming output complexities today, though. I
want to try out some APIs and see which will be reasonable for real world
use. I certainly want to avoid making changes unless there are significant
benefits, and I also don't want to add excessive complexity to the trivial
cases for the sake of these "modern" special cases.

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.
>

I'm also considering some forward looking changes to the env hash,
particularly in light of how some things may change with http 2, and also
with an eye to increasing efficiency for servers/parsers populating these
structures.


>
> --
>
> ---
> 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.
>
>
>

-- 

--- 
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.



[-- Attachment #2: Type: text/html, Size: 3083 bytes --]

      reply	other threads:[~2013-07-10  2:18 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
2013-07-10  2:18   ` James Tucker [this message]

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='CABGa_T8yN0-TRA46UR9AcbrK+W0ZPKoaOERqjJrQCU-Tc=UP7g@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).