Robert Garrett
1d7f075e0d
It's getting fiddly and awful keeping all the thread control pieces all over the place. Existing ThreadPool implementations seem a little weird, and this is a learning experience. I'll just make my own! The dispatcher constructor only creates the threads and sets up their IO channels. It has another method for serial submission of jobs. The job allocation follows a round-robin selection, but I have some concerns about starvation doing this -- consider a long running scanline render. It would make the submission call block and other threads could become available for that job. But they'll be ignored, since the round-robin assignment doesn't have any skip mechanisms.
