Hi, First of all, actors are very lightweight and you can have many of them, while an ActorSystem is heavyweight and you should not have many of that (typically you'd have one).
As for the pattern you describe - it all depends on the fine details, but if I had to implement a service that needs to get a set of details and was permitted (and required) to return partial results depending on some timeout, I'd have one actor to manage the request, sending the smaller sub requests and I'd indeed use the scheduler to cut this off if tge timeout expires. It might be useful for you to take a look at the aggregator pattern referenced from the docs. It has a lot in common with this. -- >>>>>>>>>> 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
