Rainbows! Rack HTTP server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
To: rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
Subject: Re: HTML5 WebSockets
Date: Thu, 10 Dec 2009 15:32:36 -0800	[thread overview]
Message-ID: <20091210233236.GA23608@dcvr.yhbt.net> (raw)
In-Reply-To: <20091124192430.GA4965-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>

Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org> wrote:
> Hi all,
> 
> The Revactor/ThreadSpawn/ThreadPool concurrency models *should* already
> support HTML5 WebSockets out-of-the-box right now with the respective
> TeeInput (streaming "rack.input" support).  You'll probably want to make
> sure the Rack::Chunked middleware is loaded for anything you run, but
> other than that everything should work provided you have a working
> client-side implementation...
> 
> I'm terrible at doing anything interactive on web browsers[1] and I
> don't think any current browsers out there support WebSockets natively,
> but there are ways to mimic it with JS libraries it seems.
> 
> If anybody can code anything up and put up a demo, that would be great.

The new version of Chrome supports Web Sockets, so yes, I'd like to
confirm that our streaming "rack.input" support works with Web Sockets.

As always, I'm trying to avoid GUI development myself, but may end
up having to like I did with upr (http://upr.bogomips.org/) and
gaining more gray hairs in the process :<

> I'll get around to adding a Fiber-based concurrency model which should
> work with TeeInput, too.

FiberSpawn and FiberPool have been added since and both seem to work
great.

Unconfirmed, but the IO.select()-based scheduler for these should also
give these a slight advantage when balancing between multiple worker
processes.

-- 
Eric Wong
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying


  parent reply	other threads:[~2009-12-10 23:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24 19:24 HTML5 WebSockets Eric Wong
     [not found] ` <20091124192430.GA4965-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2009-12-10 23:32   ` Eric Wong [this message]
     [not found]     ` <20091210233236.GA23608-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2009-12-11  7:48       ` Eric Wong

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-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/rainbows/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091210233236.GA23608@dcvr.yhbt.net \
    --to=normalperson-rmlxzr9ms24@public.gmane.org \
    --cc=rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/rainbows.git/

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).