- 16 Feb, 2012 1 commit
-
-
Staffan Gimåker authored
Signed-off-by: Staffan Gimåker <staffan@spotify.com>
-
- 15 Feb, 2012 12 commits
-
-
Chuck Remes authored
Cleanups to man pages
-
Pieter Hintjens authored
-
Pieter Hintjens authored
-
Pieter Hintjens authored
-
Pieter Hintjens authored
-
Pieter Hintjens authored
-
Chuck Remes authored
Fixed error in documentation build
-
Pieter Hintjens authored
-
Pieter Hintjens authored
-
Pieter Hintjens authored
This reverts commit e646ce43.
-
Pieter Hintjens authored
- anonymous contributor This reverts commit 7b7d4042.
-
Pieter Hintjens authored
Wildcard support in TCP and IPC addresses
-
- 14 Feb, 2012 3 commits
-
-
Ian Barber authored
-
-
Ian Barber authored
-
- 13 Feb, 2012 2 commits
-
-
Pieter Hintjens authored
provide type safe sockets and contexts
-
Pieter Hintjens authored
more checks for parameters of API functions
-
- 12 Feb, 2012 1 commit
-
-
niXman authored
-
- 11 Feb, 2012 4 commits
-
-
skaller authored
-
Ian Barber authored
-
-
Chuck Remes authored
fix warn unused variables
-
- 10 Feb, 2012 2 commits
-
-
niXman authored
-
Pieter Hintjens authored
Provide scatter/gather array I/O
-
- 08 Feb, 2012 5 commits
-
-
-
Ian Barber authored
-
skaller authored
We have to use an incomplete type in the interface. The definition of iovec is only in the implementation. This appears to following existing practice in 0MQ. It seems a bit flakey that zmq.h is not included in zmq.cpp, which is normal practice to ensure the implementation matches the specified interface. YMMV. I follow 0MQ style.
-
skaller authored
Also move iovec definition from implementation to interface. Not clear to me at present if an incomplete type should be used to avoid gratuitously including <sys/uio.h> in the interface. The interface can't be used with this include.
-
skaller authored
-
- 07 Feb, 2012 2 commits
- 04 Feb, 2012 3 commits
-
-
Pieter Hintjens authored
Fix comments to conform to style guide.
-
skaller authored
-
skaller authored
-
- 03 Feb, 2012 5 commits
-
-
Pieter Hintjens authored
Thread Safe Sockets.
-
Pieter Hintjens authored
Semicolon missing
-
Pieter Hintjens authored
add missing semicolon
-
Daniel Norberg authored
-
skaller authored
We use a distinct context initialisation function to specify all sockets derived therefrom will be thread safe. However the inheritance is done exclusively in the C interface. This is not really correct, but it is chosen to minimise interference with the existing C++ code, including any construct or other calls within the C++ code base. Semantically the C++ code should be unchanged, physically some data structures and extra methods are provided by they're only used from the C binding.
-