Rainbows! Rack HTTP server user/dev discussion
 help / Atom feed
From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
To: Rainbows! list <rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org>
Subject: Re: Alternatives to EventMachine for async.callback
Date: Fri, 18 Jan 2013 20:28:48 +0000
Message-ID: <20130118202848.GA30420@dcvr.yhbt.net> (raw)
In-Reply-To: <CA+-9oNc-N-rbj235oDXUPf3ex=7q8TY5o7pJBMAnqjbdGsSAtQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

"W. Andrew Loe III" <andrew-4trK/3dDa6Nl57MIdRCFDg@public.gmane.org> wrote:
> The documentation
> (http://rainbows.rubyforge.org/Rainbows/EventMachine.html)
> specifically lists EventMachine as compatible with this model. Are
> there alternative ways to get this type interface without
> EventMachine? My current application is using the EventMachine loop to
> answer requests and spawn Celluloid Actors (which are in their own
> threads) which write back to the main thread. Seems like maybe I
> should just use a Thread-per-client model? I'm currently using Sinatra
> to do the HTTP acrobatics.

Thread-per-client is a perfectly good model, especially on 64-bit.

async.callback was only added because Thin supports it; and I
don't think anybody's tried to make it work without EM.  IMHO
it's ugly.
_______________________________________________
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 index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 18:33 W. Andrew Loe III
     [not found] ` <CA+-9oNc-N-rbj235oDXUPf3ex=7q8TY5o7pJBMAnqjbdGsSAtQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-01-18 20:28   ` Eric Wong [this message]
     [not found]     ` <20130118202848.GA30420-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2013-01-18 22:04       ` W. Andrew Loe III

Reply instructions:

You may reply publically 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://bogomips.org/rainbows/

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

  git send-email \
    --in-reply-to=20130118202848.GA30420@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

Rainbows! Rack HTTP server user/dev discussion

Archives are clonable:
	git clone --mirror https://bogomips.org/rainbows-public
	git clone --mirror http://ou63pmih66umazou.onion/rainbows-public

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.lang.ruby.rainbows
	nntp://ou63pmih66umazou.onion/inbox.comp.lang.ruby.rainbows

 note: .onion URLs require Tor: https://www.torproject.org/
       or Tor2web: https://www.tor2web.org/

AGPL code for this site: git clone https://public-inbox.org/ public-inbox