Rack 2 (rack-devel@googlegroups.com)

Rack 2 (rack-devel@googlegroups.com)

[James Tucker (Google Drive)]

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

I've shared an item with you:

Rack 2
https://docs.google.com/document/d/1Ltwk-NJeJHIZy7yqLi5XBxAnclRqWwOQBOzb4EYJGO4/edit?usp=sharing

It's not an attachment -- it's stored online. To open this item, just click  
the link above.

This is a straw man start of the Rack 2 design doc / todo list. Anyone on  
rack-devel can comment, rack-core can edit. Have at it.

-- 

--- 
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: 2690 bytes --]

Re: Rack 2 (rack-devel@googlegroups.com)

[Oscar Del Ben]

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

What are the guidelines for contributing to rack 2.0? I.E. where would we
point PR to?
On Jul 4, 2013 4:59 PM, "James Tucker (Google Drive)" <jftucker@gmail.com>
wrote:

> I've shared an item with you.
>
> This is a straw man start of the Rack 2 design doc / todo list. Anyone on rack-devel can comment, rack-core can edit. Have at it.
>
> [image: Document] Rack 2<https://docs.google.com/document/d/1Ltwk-NJeJHIZy7yqLi5XBxAnclRqWwOQBOzb4EYJGO4/edit?usp=sharing>
> Google Drive: create, share, and keep all your stuff in one place. [image:
> Logo for Google Drive] <https://drive.google.com>
>
> --
>
> ---
> 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: 3243 bytes --]

Re: Rack 2 (rack-devel@googlegroups.com)

[Eric Wong]

Oscar Del Ben <oscar@oscardelben.com> wrote:
> What are the guidelines for contributing to rack 2.0? I.E. where would we
> point PR to?

I strongly prefer patches/pull-requests continue to be accepted on the
mailing list (and not dependent on single-vendor tools like GH).

-- 

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

Re: Rack 2 (rack-devel@googlegroups.com)

[Eric Wong]

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

Re: Rack 2 (rack-devel@googlegroups.com)

[James Tucker]

[-- 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 --]