From mboxrd@z Thu Jan 1 00:00:00 1970 Delivered-To: chneukirchen@gmail.com Received: by 10.227.27.68 with SMTP id h4csp176129wbc; Tue, 9 Jul 2013 19:18:46 -0700 (PDT) Return-Path: Received-SPF: pass (google.com: domain of rack-devel+bncBD75LW742ECRBBMJ6OHAKGQE2S6WTYY@googlegroups.com designates 10.49.101.78 as permitted sender) client-ip=10.49.101.78 Authentication-Results: mr.google.com; spf=pass (google.com: domain of rack-devel+bncBD75LW742ECRBBMJ6OHAKGQE2S6WTYY@googlegroups.com designates 10.49.101.78 as permitted sender) smtp.mail=rack-devel+bncBD75LW742ECRBBMJ6OHAKGQE2S6WTYY@googlegroups.com; dkim=pass header.i=@gmail.com X-Received: from mr.google.com ([10.49.101.78]) by 10.49.101.78 with SMTP id fe14mr7666060qeb.13.1373422726637 (num_hops = 1); Tue, 09 Jul 2013 19:18:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-beenthere:mime-version:in-reply-to:references:date:message-id :subject:from:to:x-original-sender:x-original-authentication-results :reply-to:precedence:mailing-list:list-id:x-google-group-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; bh=o6adkcdEInEnULbr4Hb2cHcaoptq3nWJf4b2bHJqxnI=; b=T187ivoYmWYQ4tZeXFpXs1SYENMAGSc5U8eYBv5OjYK0C/8sr5SZ/xWqSaVlvE0JBp 45yccQ6U+3G9hDjHnXaG4rOy4TFcvwLioWQbN53UeekOyJ3v0k1nen8IqepHAHxtaHfh 1rcCTgXp2Powflr1jcdz8hrjaYQ8v4uZefSDyX0vEWWiQNzFM2XTR+Mg7N3QlEsmg1VS 9u5hUtr96SbobyL6PtmegjC2g7oALLj3aRMfwC+WA3DSw5sZmYTeDbpdYH0ON+MbConR RB/AoHwKbj0xLVFD1y29sTY9RRLBjDX06GNExlbl39PXWj871PEGogIIdZUa5+ZyuFit 7ZsQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-beenthere:mime-version:in-reply-to:references:date:message-id :subject:from:to:x-original-sender:x-original-authentication-results :reply-to:precedence:mailing-list:list-id:x-google-group-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type; bh=o6adkcdEInEnULbr4Hb2cHcaoptq3nWJf4b2bHJqxnI=; b=h9RYtQNY4Usi65vmKZWXDPKNwXKO5OoSDaXj4ELwtReoZcYB8on0D01NpqYiEgE5YJ QzLwlGcw8NI0P3LGMv7mJBQmITHIgKQQLs9TWC3AHdW0F7HQE2XAtpxPJ6XWrWxG9bkV EdCS1QpjS+L/MYxBRrE2v13FkpgOxetVsELFS3XJBNJoHSvaqKbBUtn3DyaEytW9560e g3KN7eTCfRaEYiqX88nYuRpZn0tkDngPIwjwtPDwg0lQvkvozPTlwatNRKHChW8UOHWh X8cYCHSYUhQCdczhvQaCV799hwipl/3IERvBDnMYfHtrlkm6GsDqMP5yUQH25bu2vcEx jgsQ== X-Received: by 10.49.101.78 with SMTP id fe14mr832535qeb.13.1373422726246; Tue, 09 Jul 2013 19:18:46 -0700 (PDT) X-BeenThere: rack-devel@googlegroups.com Received: by 10.49.118.227 with SMTP id kp3ls2427087qeb.19.gmail; Tue, 09 Jul 2013 19:18:45 -0700 (PDT) X-Received: by 10.58.136.227 with SMTP id qd3mr3398128veb.17.1373422724985; Tue, 09 Jul 2013 19:18:44 -0700 (PDT) Received: from mail-ve0-x235.google.com (mail-ve0-x235.google.com [2607:f8b0:400c:c01::235]) by gmr-mx.google.com with ESMTPS id k12si561734vdd.2.2013.07.09.19.18.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Jul 2013 19:18:44 -0700 (PDT) Received-SPF: pass (google.com: domain of jftucker@gmail.com designates 2607:f8b0:400c:c01::235 as permitted sender) client-ip=2607:f8b0:400c:c01::235; Received: by mail-ve0-f181.google.com with SMTP id db10so5127248veb.26 for ; Tue, 09 Jul 2013 19:18:44 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.58.97.167 with SMTP id eb7mr17779549veb.45.1373422724852; Tue, 09 Jul 2013 19:18:44 -0700 (PDT) Received: by 10.220.233.141 with HTTP; Tue, 9 Jul 2013 19:18:44 -0700 (PDT) In-Reply-To: <20130706033256.GB5489@dcvr.yhbt.net> References: <20130706033256.GB5489@dcvr.yhbt.net> Date: Tue, 9 Jul 2013 19:18:44 -0700 Message-ID: Subject: Re: Rack 2 (rack-devel@googlegroups.com) From: James Tucker To: rack-devel@googlegroups.com X-Original-Sender: jftucker@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jftucker@gmail.com designates 2607:f8b0:400c:c01::235 as permitted sender) smtp.mail=jftucker@gmail.com; dkim=pass header.i=@gmail.com Reply-To: rack-devel@googlegroups.com Precedence: list Mailing-list: list rack-devel@googlegroups.com; contact rack-devel+owners@googlegroups.com List-ID: X-Google-Group-Id: 486215384060 List-Post: , List-Help: , List-Archive: Sender: rack-devel@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=089e013c5b0aa4344e04e11ee53b --089e013c5b0aa4344e04e11ee53b Content-Type: text/plain; charset=ISO-8859-1 On Fri, Jul 5, 2013 at 8:32 PM, Eric Wong wrote: > "James Tucker (Google Drive)" 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. --089e013c5b0aa4344e04e11ee53b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Fri, Jul 5, 2013 at 8:32 PM, Eric Wong <normalperson@yhbt.n= et> wrote:
"James Tucker (Google= Drive)" <jftucker@gmail.com<= /a>> 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.

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

--

---
You received this message because you are subscribed to the Google Groups &= quot;Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to rack-d= evel+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 &= quot;Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to rack-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
--089e013c5b0aa4344e04e11ee53b--