* Due to the shutdown issues the TestConductorTransport is by
default not active, but it's easy to activate it and exception
will be thrown if trying to use the featues that require it, i.e
blackhole, passThrow and throttle
* Documented
* Use withFallback to use Resizer specified in code if not configured
* Use withFallback in RemoteRouterConfig also
* Fix bug of child name in RemoteRouteeProvider
* Moved akka-remote/multi-jvm test to akka-remote-tests/multi-jvm
* Removed old test utilities that are replaced by testconductor
* Removed multi-jvm from akka-remote build, these tests are now in
akka-remote-tests
* Removed test dependencies in build that are not needed any longer
* DirectRoutedRemoteActorMultiJvmSpec replaced with
NewRemoteActorMultiJvmSpec, same thing
- instead of creating local top-level actors per pipeline, just create
one system actor through which everything is sent
- this enables storing settings (like what to throttle how) within this
actor and applying settings when connections come up later
- it also gets rid of the blocking actor creation from
NetworkFailureInjector, fixing the dead-lock
- moved also the ServerFSMs to be children of the Controller
- all actors have proper names now for easier debugging
- restructure message classes in sealed traits according to message flow
direction and include confirmed/unconfirmed status in the type
- add GetAddress query for obtaining the remote transport address of
another test participant
- add reconnects to Player
- add small DSL with runOn(node...), ifNode(node...)(<true>)(<false>)
and node(<node>):ActorPath
- rewrite TestConductorSpec to use that DSL and run within a single test
procedure instead of separate NodeX classes
- hook up that test into current multi-jvm infrastructure temporarily
for testing (will use Björn’s new remote-multi-jvm stuff later)
