This is a good example of why such a lookup is not as good an idea as it seems
at first: your hierarchy is now pretty much fixed, your actors start failing if
you change some details about their parents. A much more robust solution is to
not use actorSelection and instead just pass John’s ActorRef all the way down
to those actors which need it—either by constructor or by message.
Regards,
Roland
28 jan 2014 kl. 17:22 skrev Oleg Zhurakousky <oleg.zhurakou...@gmail.com>:
> Well, now it is and I see what your problem is.
> When dealing with router Akka will create routees based on the routing
> strategy you select, so in my case I chose RoundRobin:
> val bar =
> context.actorOf(Props[Bar].withRouter(RoundRobinRouter(nrOfInstances = 5)))
>
> So what ends up happening is Aka will manage the routees instances for you
> but those instances must be referencable, so it adds another segment to the
> hierarchy:
>
> Baz: akka://akka/user/Jane/Foo/Bar/$a/Baz
>
> Baz: akka://akka/user/Jane/Foo/Bar/$b/Baz
>
> Baz: akka://akka/user/Jane/Foo/Bar/$c/Baz
>
> Baz: akka://akka/user/Jane/Foo/Bar/$d/Baz
>
> Baz: akka://akka/user/Jane/Foo/Bar/$e/Baz
>
>
>
> where before it was just
>
> Baz: akka://akka/user/Jane/Foo/Bar/Baz
>
>
>
> So now to do a lookup with router you just need to add another ../
>
> val john = context.actorSelection("../../../../../John")
>
>
>
> Cheers
>
> Oleg
>
>
>
> On Tue, Jan 28, 2014 at 10:29 AM, Vladislav Kuzemchik <nogod.m...@gmail.com>
> wrote:
> Is Bar — router?
>
> понедельник, 27 января 2014 г., 23:16:46 UTC-5 пользователь Oleg Zhurakousky
> написал:
> Actually i think you are missing one more ../. I just built a hierarchy that
> looks like yours and it works just fine:
> //akka/user
> | \
> Jane John
> |
> Foo
> |
> Bar
> |
> Baz
>
> from Baz I can reach John
> val john = context.actorSelection("../../../../John")
>
> Here is what's going on:
> From Baz:
> '../Baz' is to self
> '../../Bar' is to Bar
> '../../../Foo' is to Foo
> '../../../../John' is to John
>
> So, from d1 you should locate C via ../../../../C
>
> Cheers
> Oleg
>
>
>
>
> On Mon, Jan 27, 2014 at 5:49 PM, Vladislav Kuzemchik <nogod...@gmail.com>
> wrote:
> Hi!
>
> I have some problem with understanding how Actor paths should be organized.
>
> For example:
>
> A
> | \
> B C
> |
> D — (router)
> | \
> d1 d2
>
> From B to C I can access with "../C" or "/user/A/C"
>
> But if we talking about d1 "../../../C" will not work but absolute path
> "/user/A/C" will still work.
>
> And in that case the easy way to say "just use absolute".
>
> But the problem is, my app is distributed, and have remote deployed routees
> and actors. I cannot use absolute.
>
> The real life case is access from one dynamically deployed routee to another
> dynamically deployed routee in distributed system.
> Absolute actor path can be calculated from data sent to routees, but I don't
> know which exactly actor system have it deployed.
>
> How should I organize this?
>
> I saw "cluster::" paths and they looks like solution, but they still in
> development. And I believe there is a good solution with current akka
> features.
>
> Thanks!
>
> --
> >>>>>>>>>> Read the docs: http://akka.io/docs/
> >>>>>>>>>> Check the FAQ: http://akka.io/faq/
> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+...@googlegroups.com.
> To post to this group, send email to akka...@googlegroups.com.
>
> Visit this group at http://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
> --
> >>>>>>>>>> Read the docs: http://akka.io/docs/
> >>>>>>>>>> Check the FAQ: http://akka.io/faq/
> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at http://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
> --
> >>>>>>>>>> Read the docs: http://akka.io/docs/
> >>>>>>>>>> Check the FAQ: http://akka.io/faq/
> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at http://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/groups/opt_out.
Dr. Roland Kuhn
Akka Tech Lead
Typesafe – Reactive apps on the JVM.
twitter: @rolandkuhn
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ: http://akka.io/faq/
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/groups/opt_out.
