@Aaronontheweb I was going through the PipeTo example and is a very good one. I have few questions and appreciate your feedback. (1) For every URL there is a FeedValidatorActor is being created. How this actor being destroyed and it's child actors too? (2) Isn't FeedParserActor really router? Is there any disadvantage with not using a router in this example? (3) When it comes to TPL, I always think about the performance. But in this example an actor is created for every URI so there are 100 actors if there are 100 URIs. Running all of them at the same time, in my opinion does not improve performance because it is IO. However the performance gain comes when the content is read and start processing. Please correct me if I'm wrong.