Alternatives to EventMachine for async.callback

Alternatives to EventMachine for async.callback

[W. Andrew Loe III]

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.

--
Andrew
_______________________________________________
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

Re: Alternatives to EventMachine for async.callback

[Eric Wong]

"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

Re: Alternatives to EventMachine for async.callback

[W. Andrew Loe III]

On Fri, Jan 18, 2013 at 12:28 PM, Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org> wrote:
> Thread-per-client is a perfectly good model, especially on 64-bit.

I'd like to get this working using the Celluloid threading, then I
don't have to manage them myself, seems harder to have sinatra do
thread-per client with is streaming code, its tied to async.callback.
_______________________________________________
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