No description
c7e157121a
* Problem when using PersistentChannel from Processor * When the seq numbers of the sending processor and the seq numbers of the PersistentChannel was out of sync the PersistentChannel did not de-duplicate confirmed deliveres that were resent by the processor. * There is a hand-off in the RequestWriter that confirms the Processor seq number, and therefore the seq number of the RequestWriter must be used in the ConfirmablePersistent from the RequestReader * More tests, covering this scenario |
||
|---|---|---|
| akka-actor/src/main | ||
| akka-actor-tests/src/test | ||
| akka-agent/src | ||
| akka-camel/src | ||
| akka-cluster/src | ||
| akka-contrib | ||
| akka-docs | ||
| akka-kernel/src/main | ||
| akka-multi-node-testkit/src/main | ||
| akka-osgi/src | ||
| akka-persistence/src | ||
| akka-remote/src | ||
| akka-remote-tests/src | ||
| akka-samples | ||
| akka-slf4j/src | ||
| akka-testkit/src | ||
| akka-zeromq/src | ||
| atmos/src/main/resources | ||
| 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 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.