@Horusiath , @Aaronontheweb is there any progress on the distributed-data? i would start porting it if none has started
anyone know how to send to a clustered consistent-hashing-pool created on another port/process? Tried doing an actorselection & tell but it doesn't get there (deadlettered). tried creating the router on the secondary client but then it's a diff actor that receives the message. not sure if i'm trying to do something i shouldn't or just missing something simple
@rogeralsing, looking good for local serialization tests. I gave it a run through a bunch of experiements in F# and didn't have any hitches. I did notice that I could not serialize a C#
Action, though (whether or not you want to support that is another question)
If you share your akka branch I will try with some more complicated/remote experiments. I had noticed with some of the other serializers that what worked fine in-process would fail across processes/remotely
For
Action, I saw the much-loathed VerificationException
I have a handful of tests that fail on my akka branch, null ref exception in the runtime code generated code .. going to take a while to debug that one :)
regarding delegates, I think those should just be ignored, it will result in really weird bugs if we start passing delegates across the wire... e.g.
Haha, ok. I will try some basic IPC with sockets by hand then :+1:
@hhko, no that is not a bug, there is simply no way to observe if there are actors processing messages. lets say you have 1 mil actors, there is simply no way to synchronize that amount of work. when you think the last one is done, the first one might have started to process again.
@rogeralsing also working well between processes :+1:
nice :)
Hello People - just wrapping my head around persistence - if I implement AtLeastOnceDeliveryActor, would I need to use a Stash as well? (I can't lose any messages and I can't assume the same host will be available).
@bobanco I've ported most of it, I'm just working on porting across the multinode tests at the minute
Is anyone working on a persistence library for ElasticSearch, ie: Akka.Persistence.ElasticSearch?
@james-andrewsmith I dont think there is tbh, havent heard of anyone
Jason Roberts has posted another Pluralsight tutorial "Implementing Logging and Dependency Injection in Akka.NET"
Could someone take a look at this?
Thanks so much! I am stucked :S
There's another Akka .NET course on PluralSight .. http://www.pluralsight.com/courses/akka-dotnet-implementing-logging-dependency-injection. I haven't even gotten to watch the first one :smile: //cc @Aaronontheweb @rogeralsing
Its awesome, I watched it earlier
I learnt about Seq :) never heard of that log store before
Hi, n00b question. If I want to send a message to an actor that is physically on the same machine, but hosted in a different process, can I just use an ActorSelection referencing for instance akka://mysystem/user/Foo, or do i need to use a remote actor ref?
you can always use an actorselection, but it needs to have the correct protocol, e.g. "akka.tcp://mysystem@localhost:8080/user/Foo"
Can anyone tell me how often the AtLeastOnceDeliveryActor retries failed messages?
@featuresnap @rogeralsing You are using Akka.Remote I'm assuming? In order to utilize "akka.tcp" you need the Akka.Remote nuget package.
@irperez @rogeralsing I did not set out to use Akka.Remote, or TCP, specifically. I wanted to do a little POC where I host an actor in a Windows service, and then have a console app (running on the same machine, but separate process) send a message into the actor system hosted on the server.
@rogeralsing Seq is made by the same guy(s) that did Serilog
oh