Rainbows! Rack HTTP server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
To: rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
Subject: Re: Single Threaded Async Responses
Date: Mon, 19 Oct 2009 11:33:39 -0700	[thread overview]
Message-ID: <20091019183339.GB11442@dcvr.yhbt.net> (raw)
In-Reply-To: <0956CE27-14FE-42DF-BAD9-CED31B09D85D-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

James Tucker <jftucker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hi Eric and anyone else listening in,
> I completed an async API for Thin quite some time ago well suited to  
> some of the design goals you have here. If you're interested we could  
> have a chat about supporting the same API designs that allow single  
> threaded reactor based concurrent responses. I believe such an API would 
> fit well in rainbows too.

Hi James,

I've looked at Thin and added this as a TODO item for Rainbows! once
EventMachine support gets added.

For now, we also have an a (more Rack-compatible[1] but certain
Unices-only[2]) API which relies on passing file descriptors to Rev in
Rainbows! 0.3.0.

[1] - The only thing that keeps it from running correctly under
      Rack::Lint is that Rack::Lint doesn't pass body#to_path calls
      to up the stack even though it _allows_ it.

[2] - Most Unices seem to support /dev/fd/#{io.fileno}
      to lookup the contents of the file descriptor table.

Eric Wong

      parent reply	other threads:[~2009-10-19 18:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-05 22:10 Single Threaded Async Responses James Tucker
     [not found] ` <0956CE27-14FE-42DF-BAD9-CED31B09D85D-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-10-05 22:56   ` Eric Wong
2009-10-19 18:33   ` Eric Wong [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-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://yhbt.net/rainbows/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091019183339.GB11442@dcvr.yhbt.net \
    --to=normalperson-rmlxzr9ms24@public.gmane.org \
    --cc=rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org \


* 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.
Code repositories for project(s) associated with this public inbox


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