Message189746
Future are explicitly about kicking off a concurrent call and waiting for a reply. They're great for master/slave and client/server models, but not particularly good for actors and other forms of peer-to-peer message passing.
For the latter, explicit pools and message queues are still the way to go, and that's why I think a concurrent.pool module may still be useful as a more obvious entry point for the thread pool implementation. |
|
Date |
User |
Action |
Args |
2013-05-21 12:21:38 | ncoghlan | set | recipients:
+ ncoghlan, sbt, Tilka |
2013-05-21 12:21:37 | ncoghlan | set | messageid: <1369138897.88.0.169281099863.issue17140@psf.upfronthosting.co.za> |
2013-05-21 12:21:37 | ncoghlan | link | issue17140 messages |
2013-05-21 12:21:37 | ncoghlan | create | |
|