From: Eric Wong <normalperson@yhbt.net>
To: rack-devel@googlegroups.com
Subject: Re: [ANN/RFC] LMGTWTY - Web Sockets for Rack+Rainbows!
Date: Thu, 17 Dec 2009 00:47:57 -0800 [thread overview]
Message-ID: <20091217084757.GA17489@dcvr.yhbt.net> (raw)
In-Reply-To: <5571C7DA-A701-4775-9F56-84CE1E9EBD30@gmail.com>
James Tucker <jftucker@gmail.com> wrote:
<snip>
> Agreed. I'm not saying "must", but I would like to request that if
> you're going to try and support asynchronous models, please do it for
> real, rather than hacking it in the way we're having to in rack / thin
> / flow / etc. The more hacks we end up with, the more people get the
> impression that this is "the right way". As it is, the lack of
> protocol - app layer separation in for example, eventmachine
> applications is appalling, and something from which the community may
> never recover. The same kind of history is about to repeat itself in
> the async + long running cycle web areas - if it hasn't already gone
> past the point of no return.
I'm glad I'm not alone in feeling the current async add-ons in Rack
servers are very hacky. I'll leave async callback support out of
Sunshowers until we can have an async spec that's as elegant the
rest of Rack.
> Like I say, I could just be too much of an efficiency ideologist. If
> you don't have the demand / desire for it, then you may not have a
> good reason to put the effort in - certainly there's nothing else in
> the middle-ground space that you're filling presently, so I don't
> think you're "losing a significant market" by not doing so. As it is,
> I know of a couple of handfuls of apps either in production or close
> to production doing relatively high load async web work in ruby, and
> those folks seem to have done alright with the nasty hack that is the
> current async.callback and deferrable body apis. Bigger deterrents to
> this area actually exist outside of the web server domain itself, as
> the 1.2+ Thin api works just fine, by contrast, there's no ORM or
> process framework for doing async work well, and the closest thing
> there really is to a "nice" async api in ruby open source at present
> is the sequel monkey patches that Aman published iirc with em-mysql.
Heh, I don't know of a single public site using Rainbows! (in any form)
nor Sunshowers in production, yet. It's winter right now and probably
not the season for Rainbows! and Sunshowers :)
> P.S. it's late, so i apologise if this is too wordy/vague.
Nope, I pretty agree with everything you said and will look forward to a
Rack 2.0 spec that covers async nicely. Meanwhile, I'll keep the focus
on 1.9 Fibers since they're largely "good enough".
--
Eric Wong
next prev parent reply other threads:[~2009-12-17 8:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 20:19 [ANN/RFC] LMGTWTY - Web Sockets for Rack+Rainbows! Eric Wong
2009-12-11 21:37 ` Eric Wong
2009-12-12 0:09 ` Daniel N
2009-12-13 9:09 ` Eric Wong
2009-12-13 20:53 ` Eric Wong
2009-12-14 0:23 ` Lakshan Perera
2009-12-14 0:51 ` Eric Wong
2009-12-14 0:57 ` Eric Wong
2009-12-14 10:41 ` James Tucker
2009-12-14 18:42 ` Eric Wong
2009-12-15 1:00 ` James Tucker
2009-12-15 4:37 ` Eric Wong
2009-12-15 11:15 ` James Tucker
2009-12-15 21:32 ` Eric Wong
2009-12-16 10:57 ` James Tucker
2009-12-16 22:14 ` Eric Wong
2009-12-17 3:23 ` James Tucker
2009-12-17 8:47 ` Eric Wong [this message]
2009-12-17 11:54 ` James Tucker
2009-12-16 12:38 ` James Tucker
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=20091217084757.GA17489@dcvr.yhbt.net \
--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).