rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: James Tucker <jftucker@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: [ANN/RFC] LMGTWTY - Web Sockets for Rack+Rainbows!
Date: Mon, 14 Dec 2009 10:41:54 +0000	[thread overview]
Message-ID: <A6B2A85E-3641-429E-8EEF-32C893DAFFD0@gmail.com> (raw)
In-Reply-To: <d44890b20912131623j3a91f1exc5b2cd212afd1535@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1758 bytes --]


On 14 Dec 2009, at 00:23, Lakshan Perera wrote:

> Hi Eric,
> 
> 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 :-)

> 
> BTW, I found a small fix is needed to get this work correctly with Google Chrome Beta. As described in Section 3.2 in IETF's "The Web Socket protocol" resource name(uri) needs to be appended when constructing the WebSocket URLs. This needs to be adhered in the WebSocket-Location value of the handshake header.
> 
> I have attached a patch which fulfills this requirement.
> 
> --
> Lakshan
> 
> On Mon, Dec 14, 2009 at 2:23 AM, Eric Wong <normalperson@yhbt.net> wrote:
> Eric Wong <normalperson@yhbt.net> wrote:
> > I've started getting Web Sockets going for Rainbows! (git version-only).
> >
> > If people like it, maybe this can be put into Rack itself (and it'll
> > have a better name and more exposure).
> 
> I'm going to call it Sunshowers for now, the old name was too hard
> for other folks to remember.
> 
> I'm going to make a release of both Rainbows!+Sunshowers later
> today, but the git versions should be ready to play with.
> 
> --
> Eric Wong
> 
> <resource_name_fix.diff>


[-- Attachment #2: Type: text/html, Size: 2573 bytes --]

  parent reply	other threads:[~2009-12-14 10:42 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 [this message]
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
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=A6B2A85E-3641-429E-8EEF-32C893DAFFD0@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).