From: James Tucker <jftucker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
Subject: Single Threaded Async Responses
Date: Mon, 5 Oct 2009 23:10:34 +0100 [thread overview]
Message-ID: <0956CE27-14FE-42DF-BAD9-CED31B09D85D@gmail.com> (raw)
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.
Kind regards,
James Tucker
next reply other threads:[~2009-10-05 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 22:10 James Tucker [this message]
[not found] ` <0956CE27-14FE-42DF-BAD9-CED31B09D85D-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-10-05 22:56 ` Single Threaded Async Responses Eric Wong
2009-10-19 18:33 ` 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=0956CE27-14FE-42DF-BAD9-CED31B09D85D@gmail.com \
--to=jftucker-re5jqeeqqe8avxtiumwx3w@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).