Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 10:47
    Aaronontheweb labeled #5962
  • 10:47
    Aaronontheweb milestoned #5962
  • 10:47
    Aaronontheweb milestoned #5836
  • 10:47
    Aaronontheweb demilestoned #5836
  • 10:47
    Aaronontheweb milestoned #5667
  • 10:47
    Aaronontheweb demilestoned #5667
  • 10:47
    Aaronontheweb milestoned #5654
  • 10:47
    Aaronontheweb demilestoned #5654
  • 10:47
    Aaronontheweb demilestoned #5449
  • 10:47
    Aaronontheweb milestoned #5449
  • 10:47
    Aaronontheweb milestoned #5414
  • 10:47
    Aaronontheweb demilestoned #5414
  • 10:47
    Aaronontheweb milestoned #5400
  • 10:47
    Aaronontheweb demilestoned #5400
  • 10:47
    Aaronontheweb milestoned #5351
  • 10:47
    Aaronontheweb demilestoned #5351
  • 10:47
    Aaronontheweb demilestoned #5247
  • 10:47
    Aaronontheweb milestoned #5247
  • 10:47
    Aaronontheweb milestoned #5217
  • 10:47
    Aaronontheweb demilestoned #5217
AndreSteenbergen
@AndreSteenbergen
While in the process I would Stash all "BeginRetrieving" events, otherwise to sequences could accidentily trigger 2 sequences running parallel
Vasily Kirichenko
@vasily-kirichenko
DeviceSource which asks the device on OnPull |> Source.pulse 250ms |> ..
AndreSteenbergen
@AndreSteenbergen
BTW don't use Self in the PipeTo (with CAPS), capture Self in a variable before that. var self = 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
Rodger Brennan
@rodgerbrennan
I've been keeping with traditional Req/Resp for the webapi/webclient. It seems like the problem would be solved more appropriately if I changed to aysnc (SignalR). But, that's one of those "I can do that in a weekend" paths :)
Vagif Abilov
@object
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?
Rodger Brennan
@rodgerbrennan
@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.
AndreSteenbergen
@AndreSteenbergen
I think I would go for the simple version at this moment; call and wait. The actor won't process stuff if I am correct in the meantime
Rodger Brennan
@rodgerbrennan
Thanks!
AndreSteenbergen
@AndreSteenbergen
Np; just don't forget to place Self in a variable first, as the reference gats lost
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();

Chandra Sekhar Manginipalli
@leo12chandu
Can grouped routers take in fully qualified routees.paths to remote actors on a cluster?
Rodger Brennan
@rodgerbrennan
I did that almost exactly in the job script. Would putting the delay in the actor's command handler have any ill effects I'm not considering?
Chandra Sekhar Manginipalli
@leo12chandu
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"
AndreSteenbergen
@AndreSteenbergen
@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 PipeTo method is what I recall is recommended; but both methods should work fine
Rodger Brennan
@rodgerbrennan
I want better hardware to work with, but I'll settle for not breaking it in production :) But, yeah, this seems to be exactly what I need.
AndreSteenbergen
@AndreSteenbergen
We have to work with, what we are given sometimes.
Chandra Sekhar Manginipalli
@leo12chandu
So far from what I searched, sounds like the routees have to be in the same ActorSystem as the router (independent of nodes) when using grouped routers. Anyone know if the routees can be on a different actorsystem?
Vasily Kirichenko
@vasily-kirichenko
does anybody know if "Reactive Applications with Akka.NET" is gonna be released, finally?
The last MEAP is rather outdated, it uses Helios in snippets, etc.
Ebere Abanonu
@eaba
@vasily-kirichenko the publisher keep changing the release date
Vasily Kirichenko
@vasily-kirichenko
:(
Ebere Abanonu
@eaba
the new release date is Sep 30, 2018
Bartosz Sypytkowski
@Horusiath
@vasily-kirichenko afaik the author has no more interest in akka.net. The book will be hopefully finished after some foreword and minor update.
Vasily Kirichenko
@vasily-kirichenko
has moved to jvm maybe :)
Bartosz Sypytkowski
@Horusiath
no, he's working in CompositionalIT and last time I've checked, he was contributing to MBrace
Hyungho Ko
@hhko
Could you recommend how to integrate MVVM with Akka.NET?
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
Hyungho Ko
@hhko
always. Is it right?
Are there another ways?
Marc Piechura
@marcpiechura
@hhko Tell is fire and forget, I.e. your command will be finished immediately, I suppose you want to trigger some action, maybe with some response and the button should be disabled during execution ? Then I would use Ask instead of Tell
If your command supports async execution ofc
anthonyhawes
@anthonyhawes
@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
Vasily Kirichenko
@vasily-kirichenko
@anthonyhawes why not just save the UI execution context and perform view model mutation in it?
AndreSteenbergen
@AndreSteenbergen
Andrey Leskov
@andreyleskov
Hey, everybody! Should it be ещ possible use akka cluster with DI? I remember somebody was telling that it is ok to serialize DI props with Hyperion with surrogates.
Chandra Sekhar Manginipalli
@leo12chandu
What is the default serializer akka.net uses for messages between actors? I know it uses protobuf for internal messages like cluster gossip, etc.
Is it Newtonsoft.JSON?
Chandra Sekhar Manginipalli
@leo12chandu
I saw somewhere its JSON and from Akka.net 1.5, the default is changed to hyperion.
Alex Hofer
@alexhofer
According to the docs @leo12chandu you are correct:
https://getakka.net/articles/networking/serialization.html
Chandra Sekhar Manginipalli
@leo12chandu
Thanks Alex