Before eventmachine is initialized or after it's been release, I put in place a Null Object that will prevent "undefined method for nil" errors. This is a fix for issue 123.
added tests for jeventmachine
prevent error when calling em methods BEFORE initialization as well.
compile for 1.5
merged with trunk
Introduce Null object for eventable channel
Why has this never been touched? Any comments?
Because EventMachine is unmantained. See #329 (comment).
Hi @garbagecat, Carsten Bormann and me forked the project into EventMachine-LE which includes various ignored pull requests and bug fixes (i.e. real and tested IPv6 support for UDP and TCP client/server). Please consider taking a look to it.
Thanks a lot.
@ibc It look like you guys dumped the java reactor though? That's too bad.
You are right, but the EM Java version was really outdated and does not include lot of changes, features and improvements in the C++ reactor.
@ibc , I'm trying to clear up a few of the JRuby issues in this repo, maybe It'd be better to add the changes to yours though?
Hi @m0wfo, eventmachine-le has no Java reactor, it was removed because it was considered not updated to the C version.
@ibc Appreciate that- the Java version needs some love. I'm rewriting the original in pure ruby so I'll check back when I have something more concrete.
Abstract out an EmReactorInterface and create a NullEmReactor and
NullEventableChannel to use when the reactor should not be running.
This is a rebase of PR #124.