From: Konstantin Haase <k.haase@finn.de>
To: rack-devel@googlegroups.com
Subject: Re: Rack asynchronous responses with async.callback
Date: Mon, 16 Apr 2012 00:40:03 -0700 (PDT) [thread overview]
Message-ID: <10094941.3386.1334562003291.JavaMail.geo-discussion-forums@vbiz13> (raw)
In-Reply-To: <11588923.816.1334536867088.JavaMail.geo-discussion-forums@vbhy13>
[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]
Hi there!
async.callback will never be part of the spec, that's true. But there will
be a completely different spec for a successor of Rack, which will include
first class support for async responses. Howerver, work is going rather
slow on that front at the moment.
At status quo, both Thin and Rainbows support just returning a Defferrable
(or really, anything that responds to both callback and errback) without
the need to an async response, rendering both the async handshake and
async.callback unnecessary. Main issue is other middleware (esp.
Rack::Lint) wrapping the body object in something that does not proxy those
methods.
Konstantin
On Monday, April 16, 2012 2:41:07 AM UTC+2, pmahoney wrote:
>
> I am doing some work with JRuby that may need asynchronous HTTP support.
> There doesn't seem to be much documentation about this online, so I did
> some digging to see how the existing Rack async servers do things, and
> wrote up some documentation for myself. I thought maybe others would find
> it useful:
> http://polycrystal.org/2012/04/15/asynchronous_responses_in_rack.html
>
> I also found some posts from a couple years ago implying that
> 'async.callback' will never be a part of the Rack specification:
>
>
> https://groups.google.com/forum/?fromgroups#!searchin/rack-devel/async/rack-devel/fu58paleLJg/frwK57QHNn4J
>
> Is this still the case? I must say I'm a bit disappointed by this
> discovery, but I don't fully understand all the issues (in particular, my
> documentation above ignores interaction with middleware).
>
[-- Attachment #2: Type: text/html, Size: 2097 bytes --]
prev parent reply other threads:[~2012-04-16 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 0:41 Rack asynchronous responses with async.callback P .
2012-04-16 7:40 ` Konstantin Haase [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=10094941.3386.1334562003291.JavaMail.geo-discussion-forums@vbiz13 \
--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).