[zeromq-dev] [PATCH] Scalability improvements for large amounts of connections

[Martin Sustrik]

On 10/11/2010 05:33 PM, Pieter Hintjens wrote:

> 1. Trying to share a socket between multiple threads. Dismissed as bad practice.
> 2. Erlang-style moving of active sockets between threads.  For
> advanced users, can be covered by "ensure full memory barrier".
> 3. Creating sockets in parent threads.  Quite common use case, and the
> only one that should be explicitly supported or documented IMO.
>
> For case 3 it should IMO either 'just work' when the socket is created
> but never used in the parent thread (doing an implicit memory barrier
> after creation, for example).

+1

Martin