Fork me on GitHub

@noisesmith I see, that kinda sounds like a poor's man threadpoolexecutor though. Not sure there's any benefit at that point.


As I mentioned, it's being able to coordinate between multiple asynchronous events that don't fit a simple map reduce model. If map reduce describes the task exactly, yeah use a queue and a thread pool.


Thanks for the details. I'll mess with it some more, I feel maybe I don't happen to have the use cases to really leverage the core.async power, but it could be I need to be a little more familiar with their details.