From: James Tucker <jftucker@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: [ANN/RFC] LMGTWTY - Web Sockets for Rack+Rainbows!
Date: Tue, 15 Dec 2009 01:00:37 +0000 [thread overview]
Message-ID: <102BE9BA-FC74-4C5C-A37B-A526C0E7A010@gmail.com> (raw)
In-Reply-To: <20091214184227.GB12789@dcvr.yhbt.net>
On 14 Dec 2009, at 18:42, Eric Wong wrote:
> James Tucker <jftucker@gmail.com> wrote:
>> On 14 Dec 2009, at 00:23, Lakshan Perera wrote:
>>> This is awesome! Thanks for coming up something like this, in a
>>> short period of time. I hope this would be part of Rack, which
>>> would enable all Ruby Frameworks to work effortlessly with
>>> WebSockets.
>>
>> I really want to work out an abstraction away from IO instances, #read
>> and #write for this stuff. It's highly coupled, getting in the way of
>> tests, and heavy lifting environments. I have big plans for Rack 2.0
>> to remove all IO that has not been properly abstracted and decoupled
>> from implementation details, but that's a long way off, mostly due to
>> lack of time and incentive. In the meantime, I can implore you all to
>> take steps in the right direction :-)
>
> Huh? I don't see what the problem with IO instances/semantics is,
> especially with the availability of StringIO for testing. "rack.input"
> is clearly specified and works fine as-is IMHO, though the rewindability
> requirement does add some unnecessary overhead.
I disagree with "works fine". It does not work fine with Thin, in fact, on the contrary, it forces some real ugliness into the system. I also think that StringIO is a really unfortunate thing to have to resort to, as it has so many short comings.
>
> --
> Eric Wong
next prev parent reply other threads:[~2009-12-15 1:00 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 [this message]
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
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=102BE9BA-FC74-4C5C-A37B-A526C0E7A010@gmail.com \
--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).