- 09 Nov, 2012 1 commit
-
-
Martin Hurton authored
-
- 27 Aug, 2012 1 commit
-
-
Arthur O'Dwyer authored
Compiling without warnings is a good goal, because it makes new warnings (which probably indicate bugs) stand out rather than getting lost in the spam. My fixes fall into two categories: - Adding (void) casts of unused parameters, where their unusedness seems like a TODO (or in some cases a bug?). - Removing parameter names altogether, where the function is clearly a stub that will never use its parameters. Should be no change in behavior.
-
- 28 May, 2012 1 commit
-
-
Martin Hurton authored
-
- 25 Mar, 2012 1 commit
-
-
Douglas Young authored
dist was skipping over pipes when one failed because the non-working pipe got swapped with a working pipe but the write was never retried on that pipe
-
- 15 Feb, 2012 1 commit
-
-
Pieter Hintjens authored
- anonymous contributor This reverts commit 7b7d4042.
-
- 10 Feb, 2012 1 commit
-
-
niXman authored
-
- 01 Nov, 2011 2 commits
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 31 Oct, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 27 Oct, 2011 1 commit
-
-
Ben Gray authored
Signed-off-by:
Ben Gray <ben@benjamg.com>
-
- 14 Sep, 2011 2 commits
-
-
Martin Sustrik authored
If several of the outbound pipes become passive while sending a single message, the refcount on the message is adjusted once only, not multiple times. It's an atomic operation so the cost is not negligible. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 01 Sep, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 23 Jun, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 20 Jun, 2011 1 commit
-
-
Martin Sustrik authored
So far there was no distinction between message parts used by 0MQ and message parts used by user. Now, the message parts used by 0MQ are marked as 'LABEL'. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 12 Jun, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 11 Jun, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 23 May, 2011 1 commit
-
-
Martin Sustrik authored
So far, the pipe termination code was spread among socket type classes, fair queuer, load balancer, etc. This patch moves all the associated logic to a single place. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 22 May, 2011 1 commit
-
-
Martin Sustrik authored
So far, there was a pair of unidirectional pipes between a socket and a session (or an inproc peer). This resulted in complex problems with half-closed states and tracking which inpipe corresponds to which outpipe. This patch doesn't add any functionality in itself, but is essential for further work on features like subscription forwarding. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 15 May, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 02 May, 2011 1 commit
-
-
Martin Sustrik authored
This patch fixes the activation of the pipes, when they pass from passive state directly to active. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 30 Apr, 2011 1 commit
-
-
Martin Sustrik authored
Reaching the HWM caused breaking message atomicity when the flow was reestablished - initial parts of multipart messages may have been lost. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 21 Apr, 2011 1 commit
-
-
Martin Sustrik authored
This patch addresses serveral issues: 1. It gathers message related functionality scattered over whole codebase into a single class. 2. It makes zmq_msg_t an opaque datatype. Internals of the class don't pollute zmq.h header file. 3. zmq_msg_t size decreases from 48 to 32 bytes. That saves ~33% of memory in scenarios with large amount of small messages. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 12 Apr, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 20 Mar, 2011 1 commit
-
-
Martin Sustrik authored
When new peer connects to a PUB socket while it is in the middle of sending of multi-part messages, it gets just the remaining part of the message, i.e. message atomicity is broken. This patch drops the tail part of the message and starts sending to the peer only when new message is started. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 02 Mar, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 14 Jan, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 06 Dec, 2010 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 04 Dec, 2010 1 commit
-
-
Martin Sustrik authored
These are just placeholders. At the moment XPUB behaves th same as PUB and XSUB as SUB. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 05 Nov, 2010 1 commit
-
-
Martin Sustrik authored
Threads were so far identified by integers called 'slots'. This patch renames them to more comprehensible 'tid's (thread IDs). Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 30 Oct, 2010 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 16 Oct, 2010 1 commit
-
-
Martin Sustrik authored
1. ZMQ_LINGER option can be set/get 2. options are part of own_t base class rather than being declared separately by individual objects 3. Linger option is propagated with "term" command so that the newest value of it is used rather than the stored old one. 4. Session sets the linger timer if needed and terminates as soon as it expires. 5. Corresponding documentation updated. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 28 Sep, 2010 1 commit
-
-
Gonzalo Diethelm authored
-
- 01 Sep, 2010 1 commit
-
-
Martin Sustrik authored
-
- 25 Aug, 2010 2 commits
-
-
Martin Sustrik authored
-
Martin Sustrik authored
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.
-
- 27 Mar, 2010 2 commits
-
-
Martin Sustrik authored
-
Martin Sustrik authored
-
- 20 Mar, 2010 1 commit
-
-
Martin Sustrik authored
-
- 13 Mar, 2010 1 commit
-
-
Martin Sustrik authored
-