I'm sorry, but your response to the perl ithreads join help!! thread has nothing whatsoever to do with my question. Is there something there on synchronized process starts? I don't see it.
| [reply] |
The second example provides a method for passing messages to the threads. You could make the messages 2-part: the first part for selecting which thread should process it, and the second part the action/message.
Receiving threads which are not the intended recpipent would re-queue it. This is slightly inefficient, but, depending on the number or syncs required, this could be a reasonable mechanism.
Offense, like beauty, is in the eye of the beholder, and a fantasy.
By guaranteeing freedom of expression, the First Amendment also guarntees offense.
| [reply] |