From: Eric Wong <normalperson@yhbt.net>
To: rack-devel@googlegroups.com
Subject: env["rack.io"] + WebSockets notes
Date: Wed, 16 Dec 2009 14:58:41 -0800 [thread overview]
Message-ID: <20091216225841.GA21990@dcvr.yhbt.net> (raw)
Eric Wong <normalperson@yhbt.net> wrote:
(in <20091216221427.GA21033@dcvr.yhbt.net>)
> With a env["rack.io"] that exposes an IO-ish object, then nothing
> prevents developers from using EM.attach or Rev::IO.new on it, either.
> If people like that, I'd be happy to include it EM and Rev-based
> concurrency models for Rainbows! and add support for it in Sunshowers.
Of course the IO object was already attached to the event loop by the
server processing the request. I suppose we could just stick the
EM::Connection or Rev::IO-based object in env["rack.io"] and then
have the Rack application do:
env["rack.io"].extend(MyWebSocketApp)
--
Eric Wong
next reply other threads:[~2009-12-16 22:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 22:58 Eric Wong [this message]
2009-12-17 2:26 ` env["rack.io"] + WebSockets notes 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=20091216225841.GA21990@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).