akkadotnet/akka.net

Port of Akka actors for .NET

Aaron Stannard

@Aaronontheweb

I found a bug in the TestConductor in the multi-node testkit that your Roslyn analyzer also found

caused tests that use throttling to crash

Roger Johansson

@rogeralsing

tlotter

@tlotter

Hi, what is the best way to communicate with a client application (Unity3D .Net 3.5) via a small protocol (ProtoBuf) with an ActorSystem? I read about Akka I/O and was wondering if this is the right way. If so, is there a client library for .Net 3.5 ?

Aaron Stannard

@Aaronontheweb

related to this

Roger Johansson

@rogeralsing

I should probably extend that to look for class member mutations too

Aaron Stannard

@Aaronontheweb

closure bug

@rogeralsing btw, are we actually using akka.actor.ask-timeoutin the C# code anywhere? I want to use that setting to kill off some potential sources of deadlock in the multi-node testkit

I can't find where we're consuming that value

Bartosz Sypytkowski

@Horusiath

@Aaronontheweb if you use Ask without explicit timeout then you're using this setting

Aaron Stannard

@Aaronontheweb

@Horusiath good, that's what I wanted to know - but where in C# do we actually load this setting? Was trying to find a place where we load the ask-timeout key from a Config object

@tlotter at the moment, no - we do not have a general client for Akka.IO just yet

it's D-I-Y

Bartosz Sypytkowski

@Horusiath

@Aaronontheweb private Futures.Ask static extension method

timeout = timeout ?? provider.Settings.AskTimeout;

Aaron Stannard

@Aaronontheweb

ah, got it!

thanks

Suhas Chatekar

@schatekar

What is C# equivalent of actor ! BroadCast(PoisonPill) ?

Bartosz Sypytkowski

@Horusiath

actor.Tell(new Broadcast(PoisonPill.Instance))

Suhas Chatekar

@schatekar

tks

Suhas Chatekar

@schatekar

I am trying to port this line

system.eventStream.publish(Mute(EventFilter.warning(pattern = ".*received dead letter from.*")))

How do I create a warning event filter in C#?

Aaron Stannard

@Aaronontheweb

yeah, we don't have good documentation on this currently

here's how you can do it though

EventFilter.Warning(pattern: new Regex(@".*received dead letter from.*")).Mute();

Bartosz Sypytkowski

@Horusiath

what is the state of Dependency Injection combined with remote deployment scenarios? Any examples?

cause right now I'm trying that one and I've got node dissassociation (with some null ref exception in the middle)

Aaron Stannard

@Aaronontheweb

what is the state of Dependency Injection combined with remote deployment scenarios? Any examples?

not supported

Bartosz Sypytkowski

@Horusiath

is that something, we should put on the issue tracker?

Aaron Stannard

@Aaronontheweb

it's something we've discussed with @rkuhn as something to consider for both Akkas in the future

definitely not a "hack this up over a weekend" sort of feature, as it has the potential to break location transparency

since it requires DI containers on both ends of the wire to have the same dependencies

errr, the appropriate configuration

so yeah, let's discuss it

could you create a discussion issue for it?

Bartosz Sypytkowski

@Horusiath

yes

Aaron Stannard

@Aaronontheweb

thanks bud :+1:

I think it'd be a kick ass feature - since as you've discovered right now, the status quo breaks location transparency quite easily too :p

Bartosz Sypytkowski

@Horusiath

yes, but you could say that requirement to have the libraries to share actor definitions across the nodes also breaks location transparency

Aaron Stannard

@Aaronontheweb

yeah, that's true I suppose

same of message types

although I guess the idea is that if you're going to have location transparency, you'd assume that you'd have 100% of the messages and actors you want to use defined locally too

Bartosz Sypytkowski

@Horusiath

personaly I don't feel need for DI in akka, but tomorrow I'll try to evangelize my team to use it, and probably it will be on the wishlist :P

Aaron Stannard

@Aaronontheweb

and in order to make that work over the network, you'd expect that code to be deployed and ready there

@Horusiath I know that feel bro

during a bunch of our consulting calls we're pitching customers on ditching SQL Server and ACID for certain workloads

and even while SQL Server is literally the single point of failure that is causing massive scaling problems for some of these guys

Aaron Stannard

@Aaronontheweb

they're still really skeptical of the alternatives :p

point being: I'm with you, I'd probably not use DI with actors

but it's hard asking people to throw away ALL of the tools they're used to using at once, so I understand why there's resistance lol :p

Where communities thrive

People

Repo info

Activity