- 09 Feb, 2016 1 commit
-
-
Pieter Hintjens authored
And I'm on a reasonably sized laptop. I think allocating INT_MAX memory is dangerous in a test case. Solution: expose this as a context option. I've used ZMQ_MAX_MSGSZ and documented it and implemented the API. However I don't know how to get the parent context for a socket, so the code in zmq.cpp is still unfinished.
-
- 28 Jan, 2016 1 commit
-
-
Constantin Rack authored
Solution: update to 2016
-
- 27 Jan, 2016 1 commit
-
-
somdoron authored
-
- 17 Dec, 2015 1 commit
-
-
Pieter Hintjens authored
This reverts commit 54799c8c. This change broke the tests/test_shutdown_stress testcase.
-
- 30 Nov, 2015 1 commit
-
-
Charles Stanley authored
-
- 09 Oct, 2015 1 commit
-
-
Charles Stanley authored
-
- 06 Sep, 2015 1 commit
-
-
Constantin Rack authored
-
- 16 Aug, 2015 1 commit
-
-
somdoron authored
-
- 05 Jun, 2015 1 commit
-
-
Richard Newton authored
-
- 02 Jun, 2015 1 commit
-
-
Pieter Hintjens authored
Of course people still "can" distributed the sources under the LGPLv3. However we provide COPYING.LESSER with additional grants. Solution: specify these grants in the header of each source file.
-
- 12 Feb, 2015 2 commits
- 22 Jan, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: update for 2015 Fixes #1320
-
- 09 Jan, 2015 1 commit
-
-
Thomas Rodgers authored
Revert "linking fd to pipe identity via socket option" This reverts commit fe3e8c5c. Conflicts: include/zmq.h src/pipe.hpp src/session_base.cpp
-
- 20 May, 2014 1 commit
-
-
Martin Hurton authored
- add const modifier to address parameter of event generating functions
-
- 30 Apr, 2014 1 commit
-
-
Stoian Ivanov authored
-
- 28 Apr, 2014 1 commit
-
-
Pieter Hintjens authored
Specifically: * zmq_event_t should not be used internally in libzmq, it was meant to be an outward facing structure. * In 4.x, zmq_event_t does not correspond to monitor events, so I removed the structure entirely. * man page for zmq_socket_monitor is incomplete and the example code was particularly nasty. * test_monitor.cpp needed rewriting, it was not clean.
-
- 19 Jan, 2014 2 commits
-
-
Pieter Hintjens authored
- renamed to ZMQ_CONNECT_RID - fixed whitespace malformating around previous patch - renamamed next_peer_id to next_rid in preparation for larger rename of IDENTITY to ROUTING_ID Note: ZMQ_CONNECT_RID has no test case and no entry in the man page, as yet.
-
Tim M authored
Fixed compile issue with missing member of socket_base. Changed ZMQ_NEXT_IDENTITY to ZMQ_NEXT_CONNECT_PEER_ID. Fixed case where ZMQ_NEXT_CONNECT_PEER_ID is used in ROUTER, and ROUTER does not read the identity message from the connected pipe.
-
- 12 Jan, 2014 1 commit
-
-
Martin Hurton authored
The get_credential () member function returns credential for the last peer we received message for. The idea is that this function is used to implement user-level API.
-
- 08 Jan, 2014 1 commit
-
-
Martin Hurton authored
-
- 07 Jan, 2014 1 commit
-
-
Stefan Radomski authored
Also moved the fd field from message content to message itself
-
- 06 Jan, 2014 1 commit
-
-
Stefan Radomski authored
This patch allows client applications to retrieve the remote endpoint from a message that originated from a tcp socket
-
- 02 Jan, 2014 1 commit
-
-
Pieter Hintjens authored
-
- 31 Aug, 2013 1 commit
-
-
Shawn J. Goff authored
icanhasall is cute (for now), but the effect of the variable is clear only after tracking down its origin reading the commit. This change is intended to make it easier for people to have some intuition about its effect from its name.
-
- 18 Aug, 2013 1 commit
-
-
Ian Barber authored
Looks like linger is honoured properly, but shutting down the session causes the pipe termination to come from that side - because the local pipe then shuts down right away it seems to trigger a terminated on the other end instead of waiting. This way we trigger the termination from the local end and then terminate the session.
-
- 29 Jun, 2013 1 commit
-
-
Martin Hurton authored
-
- 06 Jun, 2013 1 commit
-
-
Martin Hurton authored
-
- 12 Mar, 2013 1 commit
-
-
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.
-
- 08 Mar, 2013 1 commit
-
-
Guido Goldstein authored
-
- 04 Dec, 2012 1 commit
-
-
Stefan Radomski authored
- fixes LIBZMQ-476 and LIBZMQ-475
-
- 21 Nov, 2012 1 commit
-
-
Lourens Naudé authored
-
- 17 Nov, 2012 1 commit
-
-
Lourens Naudé authored
Copy monitor specific event endpoints to event messages as the engine etc. can be released at anytime
-
- 09 Nov, 2012 2 commits
-
-
Martin Hurton authored
-
Martin Hurton authored
-
- 18 Oct, 2012 1 commit
-
-
Pieter Hintjens 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
-
- 24 Aug, 2012 1 commit
-
-
Arthur O'Dwyer authored
There are three versions of monitor_event(), all taking variadic arguments. The original code just has the first one creating a va_list and passing that va_list variadically to the second one... which creates a new va_list and passes it variadically to the third one... and of course everything blows up when we try to pull a non-va_list argument off the stack. The correct approach matches the C standard library's use of printf/vprintf, scanf/vscanf, and so on. Once you make a va_list, you must pass it only to functions which expect a va_list parameter.
-
- 12 Jun, 2012 2 commits
-
-
Ian Barber authored
Revert "Fix a number of whitespace issues in various parts of the code, add validation to most calls on the test and take a first stab at implementing the reconnection pipe blocking." This reverts commit 6f6466f0.
-
Ian Barber authored
Revert "On the advice of Martin Hurton, removed the new command type and just terminated the pipe in a reconnect situation, and notified the socket of the same. This handles the blocking properly, but at the cost of potentially losing in flight messages. However, this is a reasonable trade off given how much simpler it makes the patch." This reverts commit c13f1d52.
-