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: Call for 1.1.0 release
Date: Sat, 26 Dec 2009 14:38:38 +0000	[thread overview]
Message-ID: <C08B7720-7260-4657-980E-970058DE9737@gmail.com> (raw)
In-Reply-To: <1c5622660912241540v74329427nd1053b6e602e6506@mail.gmail.com>

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


On 24 Dec 2009, at 23:40, Joshua Peek wrote:

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

+1 we need to hold off, there's more to discuss in this area.

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


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 3679 bytes --]

      parent reply	other threads:[~2009-12-26 14:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22  3:11 Call for 1.1.0 release Joshua Peek
2009-12-22 13:02 ` Christian Neukirchen
2009-12-22 22:52 ` Ryan Tomayko
2009-12-31  1:22   ` Eric Wong
2009-12-24 22:49 ` Eric Wong
2009-12-24 23:40   ` Joshua Peek
2009-12-24 23:57     ` Scytrin dai Kinthra
2009-12-25  0:24     ` Eric Wong
2009-12-26 14:41       ` James Tucker
2009-12-26 23:27         ` deferrable bodies in Rainbows! Eric Wong
2009-12-30 10:47           ` Eric Wong
2009-12-26 14:38     ` 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=C08B7720-7260-4657-980E-970058DE9737@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).