On Mon, Apr 8, 2013 at 6:26 PM, Michael Powell <[email protected]> wrote:
> If I understand it correctly, the thing that is blocked is the Context, > which needs to be protected. There's no getting around this brutal fact. Except the context provides atomic resources. There's no way to deadlock two tasks via the context. I can make a deadlockable design but it's extremely artificial. Two threads, each waiting on a specific message only the other can produce. It hardly qualifies as a deadlock. I can get the same with a single task that just sleeps forever... I'll make this claim: the classic deadlock is impossible when you use message-based tasks that don't share any state. -Pieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
