No description
ddb03c910d
* Problem: testActor subscriber sometimes didn't receive expected published message * Reason: the testActor subscribe/unsubscribe in beforeEach/afterEach via different instances of the publisher, therefore the ordering of those messages were not guaranteed, and unsubscribe happend after subscribe * Solution: subscribe directly to the eventStream once, and use separate TestProbe to verify the subscribe/unsubscribe |
||
|---|---|---|
| akka-actor/src/main | ||
| akka-actor-tests/src/test | ||
| akka-agent/src | ||
| akka-camel/src | ||
| akka-cluster/src | ||
| akka-contrib | ||
| akka-dataflow/src | ||
| akka-docs | ||
| akka-durable-mailboxes | ||
| akka-kernel/src/main | ||
| akka-osgi/src | ||
| akka-osgi-aries/src | ||
| akka-remote/src | ||
| akka-remote-tests/src | ||
| akka-samples | ||
| akka-sbt-plugin | ||
| akka-slf4j/src | ||
| akka-testkit/src | ||
| akka-transactor/src | ||
| akka-zeromq/src | ||
| project | ||
| scripts | ||
| src/main/ls | ||
| .gitignore | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.textile | ||
h1. Akka We believe that writing correct concurrent, fault-tolerant and scalable applications is too hard. Most of the time it's because we are using the wrong tools and the wrong level of abstraction. Akka is here to change that. Using the Actor Model together with Software Transactional Memory we raise the abstraction level and provide a better platform to build correct concurrent and scalable applications. For fault-tolerance we adopt the "Let it crash" model which the telecom industry has used with great success to build applications that self-heal and systems that never stop. Actors also provide the abstraction for transparent distribution and the basis for truly scalable and fault-tolerant applications. Akka is Open Source and available under the Apache 2 License. Learn more at "http://akka.io":http://akka.io.