dependabot[bot] on nuget
Bump Google.Protobuf from 3.17.… (compare)
Aaronontheweb on dev
Add backward compatibility to P… (compare)
I just found Props.CreateBy and IIndirectActorProducer, that sounds like the thing I want. Does that sound right?
Is something like that generally thinkable using Akka.NET, maybe using Akka.Remoting with a custom protocol over websocket, or by using Akka.IO and "proxy actors" which forward and filter messages?
My expectation was that the clusterclient would automatically keep track of new nodes (running a duplicate console app with a dynamic port) and would start sending messages there once the initial contact node has gone down… Am I mistaken, do I need to manually keep track of nodes?
_clusterClientis talking to a node that is dead, the remote receptionist we were previously receiving messages from is now dead
ReceiveTimeoutto detect when messages coming from the remote client actor have stopped (since we're using pub sub)
Senderfor any of the messages I receive from the cluster
ClusterClient.Sendafter I receive a
.. well kind of.. so you are saying the clusterclient keeps track of available nodes but if the cluster node my clusterclient is connected to terminates I need to instantiate a new clusterclient … why does is keep track of other receptionist nodes then? Only for the send all and publish scenarios? Feels odd
ClusterClient.Sendto do that
I mean in order to keep track of available receptionist nodes it would need to monitor members up and down events..right? why wouldn’t it handle the scenario where the receptionist it’s currently connected to is going down and simply connect to one that’s available. I Have a feeling I’m missing something obvious:( or perhaps I’m not fully understanding the purpose of a clusterclient