Using objects that manage threads via std.concurrency

[monarch_dodra]

On Tuesday, 12 February 2013 at 07:07:21 UTC, Jonathan M Davis 
wrote:
> Which I don't think was ever really intended. That doesn't mean 
> that it's
> unreasonable, but I think that it was always the idea that a 
> particular thread
> had a particular job, in which case, you wouldn't generally be 
> trying to send
> messages to different parts of the thread.
>
> - Jonathan M Davis

Hum, I just realized that "receive" works out of order on the 
types requested. I thought it *had* to receive THE first message 
in the queue, and throw if the type is not supported.

I guess then that by specifying my specific type, and having a 
dedicated dispatcher, I can make my program work, without 
clashing with anybody else who is also threading.

Now, I've just got to figure out how to manage my master's 
mailbox sizes, if a worker is faster than the rest.