Hi Ranga, Ok, so just to clarify, the third-party system cannot send a message to an actor—it only communicates responses through writing files?
Cheers, √ On Mon, Jan 20, 2014 at 8:42 PM, <rsreeniva...@gopivotal.com> wrote: > Pardon my beginner questions. The main requirement is around designing the > request handoff and handling the async result processing. A typical request > into the system would result in a call to an external third-party > component. The third-party would respond at some point in the future and > would write the results to a file system. These results should be processed > and the respective actors that created the requests should be informed. > Please let me know if I need to clarify futrher. > > > - Ranga > > > On Monday, January 20, 2014 10:45:51 AM UTC-8, √ wrote: > >> Hi Ranga, >> >> "Better" depends on what you are out to achieve, what are the >> requirements? >> >> Cheers, >> √ >> >> >> On Mon, Jan 20, 2014 at 7:02 PM, <rsreen...@gopivotal.com> wrote: >> >>> Hi >>> >>> I was wondering if someone could guide me with the following design. The >>> use-case I have is as follows: >>> >>> - Actor-A sends a request to a third-party system >>> - Third party system responds immediately with an ID for the request >>> - Actor-A sends a message to its parent with the Request-ID >>> - Third-party system processes request and creates a result that is >>> consumed by another actor (Actor-B) >>> - Actor-B should inform Actor-A or its parent about the results >>> (Request-ID is available in the results) >>> >>> I was thinking about having Actor-A send a "register" message to >>> Actor-B. On availability of results, Actor-B shall "notify" Actor-A. To >>> implement this, Actor-B shall contain a map of "Request-ID" -> "Actor-A >>> Refs". Once a message gets sent to an Actor-B ref, the corresponding entry >>> shall be taken out of the map. >>> Are there better ways of designing this? >>> >>> >>> - Ranga >>> >>> -- >>> >>>>>>>>>> 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. >>> >> >> >> >> -- >> Cheers, >> √ >> >> * ——————— **Viktor Klang* >> *Chief Architect - **Typesafe <http://www.typesafe.com/>* >> >> Twitter: @viktorklang >> > -- > >>>>>>>>>> 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. > -- Cheers, √ *———————**Viktor Klang* *Chief Architect - **Typesafe <http://www.typesafe.com/>* Twitter: @viktorklang -- >>>>>>>>>> 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.
