Comments on: EventMachine Examples http://www.mikeperham.com/2009/11/02/eventmachine-examples/ On Ruby, software and the Internet Wed, 21 Jul 2010 20:03:10 -0500 http://wordpress.org/?v=2.9.2 hourly 1 By: Chad http://www.mikeperham.com/2009/11/02/eventmachine-examples/comment-page-1/#comment-464 Chad Mon, 08 Feb 2010 03:13:39 +0000 http://www.mikeperham.com/?p=382#comment-464 Mike, I'm working on my own EventMachine based server (http://github.com/chadrem/officer). I'm just wondering if you have stumbled across any EventMachine based testing tools since writing this. Mike, I’m working on my own EventMachine based server (http://github.com/chadrem/officer). I’m just wondering if you have stumbled across any EventMachine based testing tools since writing this.

]]> By: Mars http://www.mikeperham.com/2009/11/02/eventmachine-examples/comment-page-1/#comment-442 Mars Tue, 03 Nov 2009 15:51:39 +0000 http://www.mikeperham.com/?p=382#comment-442 I had a similarly challenging go with EventMachine at Scout Labs. It's an amazing piece of work. The trick was understanding: - the main EventMachine.run block's never-exit behavior; to see exceptions, you have to rescue, EventMachine.stop_event_loop, & raise - that the main run block must return so that events can be processed; I use ProcessChannel.subscribe & push to generate the async calls from the run block - how to act like a loop inside that main block, since it must return; at the end of each iteration I use EventMachine::Timer to schedule the next iteration - how to track & limit outstanding events so that my service doesn't run out of control *Mars I had a similarly challenging go with EventMachine at Scout Labs. It’s an amazing piece of work.

The trick was understanding:

- the main EventMachine.run block’s never-exit behavior; to see exceptions, you have to rescue, EventMachine.stop_event_loop, & raise

- that the main run block must return so that events can be processed; I use ProcessChannel.subscribe & push to generate the async calls from the run block

- how to act like a loop inside that main block, since it must return; at the end of each iteration I use EventMachine::Timer to schedule the next iteration

- how to track & limit outstanding events so that my service doesn’t run out of control

*Mars

]]>