Isn't it typically that you just want to configure one or a few things of
your router, like the pool size? Then you can read that from a separate
config property.
Another solution that might work is to use wildcards in the the deployement
config path. It is still a bit fragile in respect to implem
I was actually hoping to have it all in cfg (including the round-robin
part, I don't know how would I extract it so that whole router
configuration is loaded from custom cfg section), so it is consistent with
way other actors are deployed in system. Doing it as you described is what
I wanted to
Hi Marek,
On Thu, Sep 10, 2015 at 3:34 AM, Marek Kadek wrote:
> Hi,
>
> thanks for answer. Sorry, I'm not sure I understand you - I'm still stuck
> those - could you give me an example how to deploy my worker as router,
> let's say as RoundRobinPool of 5 instances ? How would I specify it in
>
Hi,
thanks for answer. Sorry, I'm not sure I understand you - I'm still stuck
those - could you give me an example how to deploy my worker as router,
let's say as RoundRobinPool of 5 instances ? How would I specify it in
Deploy ? If I use Deploy(routerConfig = FromConfig) I still have the
rela
Hi Marek,
In this case it is better to not rely on the name of the actor since it
might depend on several things. Instead, you can specify a Deploy object on
your Props directly (programmatically). See the docs for Deploy here:
http://doc.akka.io/api/akka/2.3.13/#akka.actor.Deploy
Then you can us
Hi,
I would like to do pretty much something like this:
http://doc.akka.io/docs/akka-stream-and-http-experimental/current/scala/stream-integrations.html#actorsubscriber
that there is a ActorSubscriber, which has some children... I would like to
control deyploment of the children via external con
