* Looked into the alternativies described in the ticket, but they were complicated so ended up with simply including the uid of the sending system in the hash for selecting inbound lane. That should be good enough, until we have any real demand for something else. * This means that different lanes can be used ActorSelection messages from different sending systems, i.e. good in a cluster, but same lane will be used for all messages originating from the same system. * Added possibility to run the benchmarks with ActorSelection * Added ActorSelection to the send consistency test |
||
|---|---|---|
| .. | ||
| src | ||
| build.sbt | ||