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
Cc: rack-devel-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: deferrable bodies in Rainbows!
Date: Sat, 26 Dec 2009 15:27:32 -0800	[thread overview]
Message-ID: <20091226232732.GA26351@dcvr.yhbt.net> (raw)
In-Reply-To: <AA4E98A6-3E73-49B5-8B43-B1E7718365A9-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Moving to rainbows list

James Tucker <jftucker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Eric - I had a report from one of the async_sinatra users who tried
> out rainbows with EM, and found that the API didn't actually line up
> with what Thin was doing. I really want to devote some more time with
> this but I've been very busy. Sadly due to this I don't want to say
> stop, but, well, I want to say please check existing apps against it.
> I guess could you check async_*.ru from
> github.com/macournoyer/thin/master/tree/examples/async_*.ru, as from
> what was reported, they're not working with the rainbows
> implementation of the deferrablebody hacks.

Hi James, thhanks for the heads up.

Rainbows! doesn't handle deferrable bodies yet (I didn't look closely enough
the first time around), so it can't do everything Thin does with EM, yet.
It's already in the TODO, I'll make a mental note to work on it sooner.

-- 
Eric Wong
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying


       reply	other threads:[~2009-12-26 23:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9363563c-cbd4-498f-b9ee-b3ee83fa15b8@r5g2000yqb.googlegroups.com>
     [not found] ` <20091224224956.GB4847@dcvr.yhbt.net>
     [not found]   ` <1c5622660912241540v74329427nd1053b6e602e6506@mail.gmail.com>
     [not found]     ` <20091225002451.GA1821@dcvr.yhbt.net>
     [not found]       ` <AA4E98A6-3E73-49B5-8B43-B1E7718365A9@gmail.com>
     [not found]         ` <AA4E98A6-3E73-49B5-8B43-B1E7718365A9-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-12-26 23:27           ` Eric Wong [this message]
     [not found]             ` <20091226232732.GA26351-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2009-12-27  1:21               ` deferrable bodies in Rainbows! James Tucker
     [not found]                 ` <9D8F97A8-F08E-437E-82EE-AD885824291A-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-12-27  2:16                   ` Eric Wong
     [not found]                     ` <20091227021603.GB28140-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2009-12-27  2:32                       ` James Tucker
2009-12-30 10:47               ` Eric Wong

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=20091226232732.GA26351@dcvr.yhbt.net \
    --to=normalperson-rmlxzr9ms24@public.gmane.org \
    --cc=rack-devel-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    --cc=rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/rainbows.git/

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