Re: Call for 1.1.0 release

[Joshua Peek <josh@joshpeek.com>]

Hey Eric,

Raw io access has been on my wish list for a while. I'm totally +1 but
do you think we can hold off? I'd like to put together the release
sometime next week before the new year.

Though there was a long year gap between 1.0 and 1.1, it doesn't mean
1.2 needs to be that far off. I'd like to speed up the release
schedule for these new ideas.

On Thu, Dec 24, 2009 at 4:49 PM, Eric Wong <normalperson@yhbt.net> wrote:
> Joshua Peek <josh@joshpeek.com> wrote:
>> I'd to cut a 1.1 release before the new year. I'm going to put in the
>
> Hi, I've started adding specs for (optional) "rack.io" and Mongrel
> support as well.  It's pretty lightweight in that it just requires
> an IO.select-able IO object or StringIO (for testing)..
>
> Perhaps it can go into 1.1 with some review/comments.
>
> It's useful for at least two purposes.
>
> * It can be used to implement Web Sockets or other alternative
>  sub-protocols with the HTTP connection.
>
> * It can be used to detect client disconnects to avoid needlessly
>  performing expensive operations:
>
>  mid: <8b5b448c-d311-4472-81c3-38fd8814cd66@r5g2000prh.googlegroups.com>
>  http://groups.google.com/group/rack-devel/browse_thread/thread/5e5b52892f5e9353
>
>
> I'm also thinking of a way to integrate it with EM-based servers like
> Thin so it can be used with existing Thin deployments.
>
>
> The code is in the "rack.io" branch of my git repo:
>  * git://git.bogomips.org/rack
>  * http://git.bogomips.org/cgit/rack.git/log/?h=rack.io
>
> Shortlog:
>
> Eric Wong (2):
>      Rack::Lint understands "rack.io" env
>      add "rack.io" to Mongrel request
>
> --
> Eric Wong
>



-- 
Joshua Peek