I have been playing around trying to find a good way to do stateful actors in a hierarchy. After talking with @Aaronontheweb that HashPooling was not a good idea so I came up with a sample project. Besides adding become logic I was wondering if anyone had any thoughts or criticism on how to model this using Akka.
I was going to combine some of the ideas with what @rogeralsing posted in his blog. Anything anyone would like to share is welcome.
Any known issues with Akka running on .Net 4 ?
Dont think anyone have tried tbh
yeah me either
when I start thinking about it. There might be some TPL stuff
and there would be some minor perf issues in places where the concurrent collections are used. Those where horrible in perf in .Net 4
meh horrible is a bit much. But they weren't great.
Do you guys make .Net 4 builds ?
ah, nuget says nope.
So in short: No known issues, but its not officially supported.
@rogeralsing, what prevents us from allowing system/context.ActorOf<ISomeInterface>() using DI internally instead of the context.DI().ActorOf<T>?
@rogeralsing I think that any DI scope which effectively takes away lifecycle management from the ActorSystem, are not supported. Because it would mean that an Actor could be disposed without the Actor system being aware of it, or being the one who actually starts the dispose. Which in turn would cause all kinds of wierd stuff. As far as i can tell.
But maybe you guys have some voodoo code to manage those scenario's.
@nvivo nothing. Just that when you do that with Actor types. They wont be initialized properly. I take you mean something like this? :
This message was deleted
what I mean is more the semantics than the implementation
imagine I have an actor that requires constructor parameters
today I'm required to create the props with DI or manually, and then pass to ActorOf
this creates 2 different ways to declare exactly the same thing
man.... personally I can explain things much better