Hi Derek, Thanks a lot for the reply!
I am not sure I get what you are saying exactly, I am trying to understand: As long as the original sender is used to reply, a1 is the sender, so if we are replying back to a1 from say a2 (the original receiver) but from another invocation of a2 "receive" method by say a3 (if possible by Akka),,, will it be linked back to a1? (how if so, the mapping is what is puzzling me if it is at all possible for above scenario, how is it done in the ActorSystem?) Thanks and best, Mo On Friday, March 25, 2016 at 3:15:54 AM UTC-6, Derek Williams wrote: > > The sender for the message will be linked back to the specific Future. As > long as the original sender is used to reply, the expected Future will be > completed. > > On Thu, Mar 24, 2016 at 7:28 PM Mohammed Al-Mahfoudh < > [email protected] <javascript:>> wrote: > >> Hi there, >> >> >> We are developing a tool to aid Akka's developers reason about programs. >> >> >> We will be very grateful if someone could help us educate our self about >> >> how "Futures" and "Ask" pattern is handled in Akka. >> >> >> So our questions are as follow: >> >> - If an ask statement, that sends a message *m1* from *a1* to *a2* >> (actors), must *a2* reply right away in the same "receive" invocation? >> or we can have another *receive* invocation reply to that ask? (I mean >> by reply also resolving the future) >> >> - How can that be implemented (abstractly speaking) since *a2* doesn't >> have an explicit handle for the Future object returned by the above ask? >> >> - Is there a "mapping" between which message sent back to *a1* >> resolves which Future it asked for? If so, how to map that? (do you >> encapsulate the original message *m1* inside the later message sent from >> a1 to a2 for replying, and then the ActorSystem knows how to resolve that >> Future in the destination actor?) >> >> >> We need to know about this since our model is to be kept more generic >> than how Akka does that but the front-end that is to parse Akka needs to do >> these specifics and puts them in terms of our model. >> >> >> Thanks a lot in advance and all appreciation! >> >> -- >> >>>>>>>>>> Read the docs: http://akka.io/docs/ >> >>>>>>>>>> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> >>>>>>>>>> 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 [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at https://groups.google.com/group/akka-user. >> For more options, visit https://groups.google.com/d/optout. >> > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
