I’ll put Camel on the list to investigate. Good luck with your code, - charlie
On Jan 20, 2014, at 4:39 PM, [email protected] wrote: > Thanks Charlie. Will go with the original design of "registering" ActorA with > ActorB and notify ActorA when a result is available. > > > - Ranga > > On Monday, January 20, 2014 2:57:24 PM UTC-8, Robert Withers wrote: > Sorry, I was being somewhat facetious, here. I work on a personal project > using promise pipelining and I am looking to port the top layer to Akka, so I > have my student’s sandals on. Your statement of passing the result from the > 3rd-party system to Actor-B, and it would resolve the original request, in > Actor-A, is what made me think of promise pipelining. Akka will do nicely > here, perhaps by passing the ActorRef to Actor-B in the original send. > > Cheers, > charlie > > On Jan 20, 2014, at 2:32 PM, [email protected] wrote: > >> Thanks Robert. Could you point me to some documentation around this? >> >> >> - Ranga >> >> On Monday, January 20, 2014 11:08:19 AM UTC-8, Robert Withers wrote: >> Promise pipelining. A solution looking for a good problem! ;) >> >> - charlie >> >> >> On Jan 20, 2014, at 11:45 AM, √iktor Ҡlang <[email protected]> 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, <[email protected]> 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 [email protected]. >>> To post to this group, send email to [email protected]. >>> 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 >>> >>> 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 [email protected]. >>> To post to this group, send email to [email protected]. >>> 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 [email protected]. >> To post to this group, send email to [email protected]. >> 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/akka-user. > For more options, visit https://groups.google.com/groups/opt_out. - robert -- >>>>>>>>>> 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/groups/opt_out.
