On Thu, Feb 16, 2012 at 6:32 PM, john skaller <[email protected]> wrote:
> No need to change it at all. It is the same as now: if you misuse a feature, > you can't > expect reliable results. > > The difference is now you get unexpected results instead of a segfault. There needs to be a very clear explanation of how to safely use sockets from multiple threads, then. It's one of those areas that causes endless problems. One thread closing a socket while another tries to use it, etc. After a lot of this, we finally just said "do not use sockets in multiple threads, period". Now this becomes possible again, people will use it, and will get it wrong. That's one risk I see. The second risk is that the design is not complete, and people not using it, means it won't mature in time for a 3.1 stable release. I'm not arguing against the feature but we need some positive feedback from people using it, IMO. John, if you had a single clear use case yourself, code which is ugly and fragile without this, and simpler with it, that would help a lot. -Pieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
