Eg if you want to async fill a grid or something
that's important
Maybe a reactive gui app for stock prices are a good example
There is also a pinned thread dispatcher, if you want to dedicate an entire thread to a specific actor
And the forkjoindispatcher, that has its own dedicated threadpool, to avoid noisy neigbours. Eg if some actors are more important than others, it can be isolated from the default shared threadpool
So that confirms my remarks about not supporting any DI lifetime scope except Transient/InstancePerDependency
it depends on what you mean with scope i guess, lets say you have one dependency that should be recreated for each usage in a dependency graph, that ofc works, and of there is some dependency that should be unique per resolve, that would work too... Eg if a foo have a ref to 5 bars and 3 baz. It could be resolved as 5 bars and one single baz. For the same foo, if foo is injected to the actor
@rogeralsing please correct if I'm wrong. Most of the JVM akka docs say that hocon configuration overrides code config. But some tests I did here shows the opposite. For example, if you specify WithRouter(...) in code, it overrides any hocon config. Is it correct that Akka.net gives preference to code over config or I missed something?
@rogeralsing I'll do a write-up about this for the http://getakka.net/docs/Dependency%20injection page. Ill run it by you guys when im done.
General question to whomever can answer this :P. My ActorSystem behaves in such a way, that it can be in an 'idle' state. Which effectively means that the mailboxes for a few key Actors in my system are empty. Does Akka currently has a way for a user of the framework to monitor this kind of state for an actor ?
So something along these lines:
where the "areyoubusy" is a system(?) message which tells me if there are messages in the actor1's mailbox
depending on the size of your changes
@Danthar by chance I'm looking at the resizer implementation. It seems that if you create a custom router, you can use ActorRefRoutee to lookup this information: https://github.com/akkadotnet/akka.net/blob/dev/src/core/Akka/Routing/Resizer.cs#L245
and set the flags on request response. this of course depended on all answers going back to the actor I had
this model is so flexible there are many ways to do the same thing
Thats why I was asking if there is anything in Akka right now, that can be used to achieve the same thing. Without me having to manually implement it.
There's a lot of complexity there that would have to be handled. My thought was that possibly the Akka wire protocol was defined to help handle some of it....not really just worried about the transport here.