- 12 Mar, 2013 3 commits
-
-
Pieter Hintjens authored
-
Pieter Hintjens authored
* Starting draft ZMTP/2.1 protocol (revision 2) * Basis for adding security to the wire protocol * Maintains backward compatibility
-
Pieter Hintjens authored
Copyrights had become ads for Sustrik's corporate sponsors, going against the original agreement to share copyrights with the community (that agreement was: one line stating iMatix copyright + one reference to AUTHORS file). The proliferation of corporate ads is also unfair to the many individual authors. I've removed ALL corporate title from the source files so the copyright statements can now be centralized in AUTHORS and source files can be properly updated on an annual basis.
-
- 01 Feb, 2013 1 commit
-
-
Min(Dongmin Yu) authored
When we send a large message, the message can be splitted into two chunks. One is in the encoder buffer and the other is the zero-copy pointer. The session could get the term before the last chunk is sent.
-
- 02 Jan, 2013 1 commit
-
-
Matt Arsenault authored
Fix warnings with ICC.
-
- 17 Nov, 2012 1 commit
-
-
Lourens Naudé authored
This reverts commit 1a18c7b0, reversing changes made to bef9a41b.
-
- 16 Nov, 2012 1 commit
-
-
Lourens Naudé authored
-
- 13 Nov, 2012 1 commit
-
-
Martin Hurton authored
-
- 21 Sep, 2012 1 commit
-
-
Lourens Naudé authored
Significantly reworked the monitoring infrastructure with a more granular per socket API and to play well with monitoring endpoints in application threads
-
- 05 Sep, 2012 2 commits
-
-
Martin Hurton authored
-
Martin Hurton authored
-
- 03 Sep, 2012 1 commit
-
-
Martin Hurton authored
-
- 02 Sep, 2012 2 commits
-
-
Martin Hurton authored
Since ZMQ 2.x does not support subscription forwarding, it's not possible to use ZMQ 2.x SUB socket to receive messages from a PUB socket. This patch adds some compatibility layer so that ZMQ 2.x SUB socket receives messages from PUB socket.
-
Martin Hurton authored
The new protocol adds support for protocol version and exchanges the socket type, so that the library can reject a connection when the sockets do not match. The protocol was designed so that it's possible to detect and fully support ZTP/1.0 peers. When a new connection is set up, peers exchange greeting messages. The greeting message encodes both the protocol verion and the socket type. The format of the greeting message is as follows: greeting = tag1, adaptation, tag2, version, length, socket_type tag1 = BYTE / 0xff adaptation = 8 BYTES tag2 = BYTE / 0x7f version = BYTE / 1 length = BYTE / 1 socket_type = BYTE The protocol does not define the value of adaptation field. When interoperability with ZTP/1.0 peers is required, the adaptaion encodes, in network byte order, the length of identity message increased by 1. When adaptaion consists of eight zeros, the current implementatatio of 0MQ 2.x closes the connection. This patch supports both ZTP/1.0 and new protocol.
-
- 04 Aug, 2012 1 commit
-
-
Lourens Naudé authored
-
- 27 May, 2012 1 commit
-
-
Martin Hurton authored
-
- 04 May, 2012 1 commit
-
-
Lourens Naudé authored
-
- 29 Apr, 2012 1 commit
-
-
Martin Hurton authored
Before this patch, the stream engine terminated itself whenever it had detected an IO error. If this happened when sending a message, the engine lost all in-flight messages, messages waiting to be decoded, and the last decoded message that had not been accepted, if there was one. The new behaviour is to terminate the engine only after the input error has been detected and the last decoded
-
- 09 Nov, 2011 1 commit
-
-
AJ Lewis authored
Older versions of gcc have problems with in-line forward declarations when there's a naming conflict with a global symbol. Signed-off-by:
AJ Lewis <aj.lewis@quantum.com> Expand the original patch to all such forward declarations. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 01 Nov, 2011 1 commit
-
-
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>
-
- 15 Sep, 2011 1 commit
-
-
Martin Sustrik authored
This is a preliminary patch allowing for socket-type-specific functionality in the I/O thread. For example, message format can be checked asynchronously and misbehaved connections dropped straight away. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 16 Aug, 2011 1 commit
-
-
Martin Sustrik authored
The engine was not used exclusively for TCP connections. Rather it was used to handle any socket with SOCK_STREAM semantics. The class was renamed to reflect its true function. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 28 Jul, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 25 Jul, 2011 1 commit
-
-
Martin Sustrik authored
zmq_engine and tcp_socket merged into tcp_engine zmq_connecter and tcp_connecter merged into tcp_connecter zmq_listener and tcp_listener merged into tcp_listener Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 24 Jul, 2011 1 commit
-
-
Martin Sustrik authored
Removal of ZMQ_IDENTITY resulted in various session classes doing almost the same thing. This patch merges the classes into a single class. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 27 Jun, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 02 Mar, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 13 Jan, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 17 Dec, 2010 1 commit
-
-
Dhammika Pathirana authored
Signed-off-by:
Dhammika Pathirana <dhammika@gmail.com>
-
- 30 Oct, 2010 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 19 Sep, 2010 2 commits
-
-
Martin Sustrik authored
-
Martin Sustrik authored
-
- 31 Aug, 2010 1 commit
-
-
Martin Sustrik authored
-
- 25 Aug, 2010 2 commits
-
-
Martin Sustrik authored
-
Martin Sustrik authored
-
- 20 Mar, 2010 1 commit
-
-
Martin Sustrik authored
-
- 12 Mar, 2010 1 commit
-
-
Martin Hurton authored
This commit introduces the necessary changes necessary for implementing flow control. None of the socket types implements the flow control yet. The code will crash when the flow control is enabled and the thw lwm is reached. The following commits will add flow-control support for individual socket types.
-
- 16 Feb, 2010 1 commit
-
-
Martin Sustrik authored
-
- 13 Feb, 2010 1 commit
-
-
Martin Sustrik authored
-