- 12 Mar, 2013 2 commits
-
-
Pieter Hintjens authored
-
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 2 commits
-
-
Guido Goldstein authored
-
Guido Goldstein authored
Simplified the zmq_event_t structure for easier access and better usability towards language bindings.
-
- 19 Feb, 2013 2 commits
-
-
Sébastien Rombauts authored
- when compiling for Windows CE, a C++ project must define the preprocessor definitions: UNDER_CE=$(CEVersion),_WIN32_WCE=$(CEVersion) - choosing the "_WIN32_CE" form for uniformization with "_WIN32" and "_WIN32_WINNT" already used in libzmq (boost is using both forms) - see http://msdn.microsoft.com/en-us/library/ee479161(v=winembedded.60).aspx
-
Sébastien Rombauts authored
Fixed 7 MSVC2008 Compiler Warning (level 3) C4800: 'const int' : forcing value to bool 'true' or 'false' (performance warning) - added explicit test "(xxx != 0)" to get a "bool" value out of the "int" expression - see the MSDN recommandation http://msdn.microsoft.com/en-us/library/b6801kcy(v=vs.90).aspx
-
- 31 Jan, 2013 2 commits
-
-
Pieter Hintjens authored
-
Pieter Hintjens authored
-
- 02 Jan, 2013 2 commits
-
-
Matt Arsenault authored
-
Matt Arsenault authored
-
- 04 Dec, 2012 4 commits
-
-
Stefan Radomski authored
-
Stefan Radomski authored
-
Stefan Radomski authored
-
Stefan Radomski authored
- fixes LIBZMQ-476 and LIBZMQ-475
-
- 22 Nov, 2012 1 commit
-
-
Lourens Naudé authored
-
- 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
-
- 14 Nov, 2012 1 commit
-
-
Lourens Naudé authored
-
- 09 Nov, 2012 4 commits
-
-
Martin Hurton authored
-
Martin Hurton authored
-
Martin Hurton authored
-
Martin Hurton authored
-
- 29 Oct, 2012 1 commit
-
-
Martin Hurton authored
-
- 24 Oct, 2012 1 commit
-
-
Pieter Hintjens 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
-
- 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.
-
- 26 Aug, 2012 2 commits
-
-
Ian Barber authored
VA specific monitor event in socket base was named monitor_event rather than va_monitor_event
-
Ian Barber authored
The call to the va version of the function was using 'event' instead of 'event_'
-
- 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.
-
- 11 Aug, 2012 1 commit
-
-
Martin Hurton authored
Fixes #415.
-
- 17 Jul, 2012 1 commit
-
-
Martin Hurton authored
-
- 06 Jul, 2012 1 commit
-
-
Martin Hurton authored
-
- 12 Jun, 2012 7 commits
-
-
Ian Barber authored
This patch, salvaged from a trainwreck accidental merge earlier, adds a new sockopt, ZMQ_DELAY_ATTACH_ON_CONNECT which prevents a end point being available to push messages to until it has fully connected, making connect work more like bind. This also applies to reconnecting sockets, which may cause message loss of in-queue messages, so it is sensible to use this in conjunction with a low HWM and potentially an alternative acknowledgement path. Notes on most of the individual commits can be found the repository log.
-
Ian Barber authored
Revert "After speaking with Ben Gray and the discussion on the mailing list, this is an attempt to create a sockopt to allow connecting pipes to not immediately be available for traffic. The problem is in a PUSH to many PULL situation, where there is a connect to a PULL which is not there. This connect will immediately create a pipe (unlike bind), and traffic will be load balanced to that pipe. This means if there is a persistently unavailable end point then the traffic will queue until HWM is hit, and older messages will be lost." This reverts commit fe3fb419.
-
Ian Barber authored
Revert "Remove the extra outpipe handling as the session is quite capable of delaying the creation of the pipe until the connection has happened. Simply don't build the pipe, and let it do that automatically." This reverts commit 06485d92.
-
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 "Fix condition so that PGM and EPGM sockets always create pipes immediately, even if delay_attach_on_connect is set. This allows passing through the icanhasall flag, and is realistic given the fact those protocols should be able to connect immediately" This reverts commit b5ace39e.
-
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.
-
Ian Barber authored
Revert "Use the hiccup mechanism to notify the socket end of the pair of the change in state, and have it shutdown that end, and shutdown the local end normally. This seems to resolve the shutdown and race condition issues." This reverts commit 67497a26.
-