These are chat archives for akkadotnet/akka.net
@Aaronontheweb - How do I death watch on IActorRef from a class that is not subclassed from ReceiveActor? It just has access to ActorSelection or Client ActorSystem.
Was able to use the ResolveOne on ActorSelection to be able to successfully send messages to the remote actor on a cluster from outside the cluster. But the issue with Deathwatching this is, deathwatch requires Context.Watch() which is only available on a ReceiveActor subclass.
I don't understand why Akka.IO has both TCP and UDP classes, but the Akka Transport only supports TCP
@nathvi Akka.Remote doesn't use Akka.IO... yet ;)
So there's no way to simulate a deterministic scheduler for multithreaded .net apps?
I thought I saw someone was in the early stages of getting one working, but I don't remember clearly :/
I think the TL;DR should be:
"partitions are most often temporary in nature and we should be hesitant to treat unreachable nodes as though they’re permanently offline.”