Why use await, when pipeTo pattern provides clean, non-blocking integration between Futures and Actors? As far as I know, the only situation when blocking in actor code is justifiable is interacting with legacy code that just blocks the calling thread and offers no way around it, like JDBC does. Of course one should use a dedicated dispatcher then, to avoid starving regular actors of resources.
W dniu poniedziałek, 20 lutego 2017 12:56:42 UTC+1 użytkownik Alan Burlison napisał: > > > This is not a solution because it creates one new thread for every > blocker. > > In general I agree, but if the code has already aggregated all the > futures into a single one, as seems to be suggested in an earlier > email, wouldn't it be an option - albeit not an ideal one? > > -- > Alan Burlison > -- > -- >>>>>>>>>> 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.
