eventmachine

EventMachine: As I understood DHH's speech, the idea is that ActionCable abstracts all the messiness around EventMachine, Websockets, Rack and threads.

So the model is a combination of EventMachine + Threads.

There are also background job processing frameworks like sidekiq and parallel job processors like celluloid, parallel and EventMachine.

EventMachine: As I understood DHH's speech, the idea is that ActionCable abstracts all the messiness around EventMachine, Websockets, Rack and threads If you are using Event Machine you can't abstract away from it.

Actually that error is being thrown when the shell command hits EventMachine::popen hmm...

The choice of I/O model has nothing to do with Ruby (see eventmachine for a commonly-used evented NIO setup).

Cable is currently using EventMachine because it uses faye-websocket for dealing with websockets.

And as DHH pointed out on twitter Clearing up misconception re: Action Cable: EventMachine only used for connection handling, threads for channel code.

Node and nginx use the same model for io, as does Tornado and Eventmachine (though the latter two are nowhere near as popular).

Tried EventMachine in the past but not with this particular use case.

Celluloid (the actor model) is vastly superior to EventMachine in my opinion.

I am positive that bringing any EventMachine technology into the Rails stack would be a mistake.

Eventmachine itself is in kinda unmaintained state.