You could have a pauze Flow stage between every step. SourceActor would be job to get all calls from 1 IOT device, every Outlet could be given to a wait Flow Inlet, Passing the result to the next Inlet
and wait 250ms after each result and use (await Thread.Delay (250)).ContinueWith(t => EVENT To Trigger Next Stage).PipeTo(Self)
@vasily-kirichenko Nice ;) but I raised this idea because of this message: "I may have to change my architecture approach a bit"
And after reading the question twice The OnPull would be non trivial, as I suspect the event/message is different in the sequence
GetTemp(); wait 250ms GetPowerLevels() wait another 15 minutes
Hello, I noticed that remote ActorSelection from a cluster node does not work the same way as when executed from a standalone app. From a Cluster node I am trying to remotely select an actor using fully qualified remote address with machine name, and selection resolution times out. But if I first create a new actor system and execute the same code with the same remote address from the newly created system it will works fine. Is there anything to be aware of when doing remote actor selection in a cluster?
@AndreSteenbergen that's pretty much it. But it's RecordTemp();wait 250ms;RecordPowerLevels(); and the events are recorded to EventStore with TempRecorded, and PowerLevelsRecorded. The hardware is my problem point because if a call is made while another is processing it'll either be ignored or worse cause the device to hang.
gets lost
I haven't used it, but if I am correct you can also use async methods in actors since 1.??.?? don't know the exact version
await iotClient.RecordTemp();
await Thread.Delay(250);
await iotClient.RecordPowerLevels();
So I can route the messages sent to this round-robin-group to an actor on a separate cluster. Tried something like routees.paths = ["akka.tcp://MyActorSystem@Machine:port/user/myactor"], but it throws "is not a valid relative actor path. Parameter name: routeesPaths"
@Horusiath answered it on stackoverflow: https://stackoverflow.com/questions/47709420/is-it-safe-to-use-async-await-inside-akka-net-actor It stops taking in new messages. What basically is what you want if I am reading your question correctly
The last MEAP is rather outdated, it uses Helios in snippets, etc.
always call Tell method of actor in Command Handler.
I don't think it's the good way.
this is sample code.
I must simply call the Tell method on all Command-Message handling functions.
This message was deleted
Are there another ways?
If your command supports async execution ofc
@hhko I have used a combination of two actors with MVVM, a UI actor which is passed the instance of the view model in it's constructor and a service actor which does work in the background. View model commands use Tell to send messages to the service actor and pass the UI actor as the sender, so all responses from the service are handled by the UI actor which can safely set properties on the view model
@anthonyhawes Nice blog MVVM / Akka: https://blog.aaronlenoir.com/2016/04/20/integrating-wpf-and-akka-net-2/