Magnus, hi!
Thanks for the suggestions!
On Monday, May 18, 2015 at 3:57:00 PM UTC+3, Magnus Andersson wrote:
1. Keep track of running futures in your actor1 in a var. When your
actor enters poststop you can await the completion of all referenced
futures. You probably would have
The Lifecycle of the Actor System does manage futures you spawn within your
Actors. You have to manage that yourself.
Two suggestions:
1. Keep track of running futures in your actor1 in a var. When your
actor enters poststop you can await the completion of all referenced
futures. You
On 05/18/15 08:01, Andrew Gaydenko wrote:
Magnus, hi!
Thanks for the suggestions!
On Monday, May 18, 2015 at 3:57:00 PM UTC+3, Magnus Andersson wrote:
1. Keep track of running futures in your actor1 in a var. When
your actor enters poststop you can await the completion of all
On Monday, May 18, 2015 at 9:33:28 PM UTC+3, Michael Frank wrote:
i usually solve this by map()ing the future to some request id that i
generate. for example (written on the spot, may not compile)
Michael,
Aha, I see, it's very smart. Will try. Thanks!
--
Read the docs:
On 05/18/15 10:31, Andrew Gaydenko wrote:
On Monday, May 18, 2015 at 7:51:31 PM UTC+3, Michael Frank wrote:
How about piping the result of the future back to actor1, then
send the result to actor2? you can prune the completed future in
actor1 when it receives the result.
Michael,
Michael,
I have implemented the idea in my context. Yes, it does work. Thanks again!
--
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
cool, glad it works!
-Michael
On 05/18/15 15:27, Andrew Gaydenko wrote:
Michael,
I have implemented the idea in my context. Yes, it does work. Thanks
again!
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the
