diff options
| author | Martin Sustrik <sustrik@250bpm.com> | 2010-08-06 17:49:37 +0200 |
|---|---|---|
| committer | Martin Sustrik <sustrik@250bpm.com> | 2010-08-25 15:39:20 +0200 |
| commit | 05d908492dc382941fc633ad7082b5bd86e84e67 (patch) | |
| tree | ae10e49766152e42521a6c100e622dc616998143 /src/zmq_encoder.cpp | |
| parent | b7e0fa972f45d21e45cacb93a1a92d38fdc11f40 (diff) | |
WIP: Socket migration between threads, new zmq_close() semantics
Sockets may now be migrated between OS threads; sockets may not be used by
more than one thread at any time. To migrate a socket to another thread the
caller must ensure that a full memory barrier is called before using the
socket from the target thread.
The new zmq_close() semantics implement the behaviour discussed at:
http://lists.zeromq.org/pipermail/zeromq-dev/2010-July/004244.html
Specifically, zmq_close() is now deterministic and while it still returns
immediately, it does not discard any data that may still be queued for
sending. Further, zmq_term() will now block until all outstanding data has
been sent.
TODO: Many bugs have been introduced, needs testing. Further, SO_LINGER or
an equivalent mechanism (possibly a configurable timeout to zmq_term())
needs to be implemented.
Diffstat (limited to 'src/zmq_encoder.cpp')
| -rw-r--r-- | src/zmq_encoder.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/zmq_encoder.cpp b/src/zmq_encoder.cpp index 077286f..d552c61 100644 --- a/src/zmq_encoder.cpp +++ b/src/zmq_encoder.cpp @@ -52,7 +52,7 @@ bool zmq::zmq_encoder_t::size_ready () bool zmq::zmq_encoder_t::message_ready () { // Destroy content of the old message. - zmq_msg_close(&in_progress); + zmq_msg_close (&in_progress); // Read new message. If there is none, return false. // Note that new state is set only if write is successful. That way |