Hi Mato, Can you review this patch?
Thanks. Martin
>From 34ff315c408a373c76ee0db32b4075dd96e98462 Mon Sep 17 00:00:00 2001 From: Martin Sustrik <[email protected]> Date: Fri, 20 May 2011 00:38:44 +0200 Subject: [PATCH] Sesion about thread-safeness in zmq(7) simplified The deleted section, while technically correct, haven't described the best practice, which made the text confusing. Signed-off-by: Martin Sustrik <[email protected]> --- doc/zmq.txt | 5 ----- 1 files changed, 0 insertions(+), 5 deletions(-) diff --git a/doc/zmq.txt b/doc/zmq.txt index 0c29a74..191fe13 100644 --- a/doc/zmq.txt +++ b/doc/zmq.txt @@ -49,11 +49,6 @@ the caller. Individual 0MQ 'sockets' are _not_ thread safe except in the case where full memory barriers are issued when migrating a socket from one thread to another. -In practice this means applications can create a socket in one thread with -_zmq_socket()_ and then pass it to a _newly created_ thread as part of thread -initialization, for example via a structure passed as an argument to -_pthread_create()_. - Multiple contexts ^^^^^^^^^^^^^^^^^ -- 1.7.0.4
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
