Finally I'm able to get CZMQ to build on Windows 7 using the Visual Studio
2013 solution. However there are a couple of issues;
Without this section commented out of czmq_prelude.h then the build gave
many errors relating to int8_t redefinition. N.B. This computer has Mingw
installed if that
I believe this condition is bogus:
|| (defined (__MINGW32__) defined (__IS_64BIT__)) \
Try removing it.
On Wed, Jan 7, 2015 at 11:48 AM, Riskybiz riskybizl...@live.com wrote:
Finally I’m able to get CZMQ to build on Windows 7 using the Visual Studio
2013 solution. However there are a
From the NEWS file:
0MQ version 4.1.0 rc1, released on 2014/10/14
=
* All issues that were fixed in 4.0.x
* Improved client reconnection strategy on errors
* GSSAPI security mechanism
* SOCKS5 support (ZMQ_SOCKS_PROXY)
OK, thanks for the reminder.
On Wed, Jan 7, 2015 at 1:28 PM, Peter Kleiweg pklei...@xs4all.nl wrote:
I noticed on the download page there are now versions 4.1.0
(release candidate), 4.0.5, and 3.2.5. None of these releases
were announced on zeromq-announce.
Please post all releases on
On 7 January 2015 at 04:05, Meng Zhuo mengzhuo1...@gmail.com wrote:
After I set rate with 31415, log shows zeromq had accepted it.
but the OpenPGM still shows Setting ODATA rate regulation to 12500 bytes
per second.
Try setting the Rate before issuing the Connect() on the socket.
--
Actually, it's even worse than that. For a standard install, I can use
only one type per platform. It has to be either SOCKET or UINT_PTR on all
Windows platforms.
I don't know why there are two different types used on Windows, but this
aspect of fd_t has been there since the initial commit
By the way, the reason such defines appear is to attempt to distinguish
between mingw32 and mingw64. Both define __MINGW32__ but unfortunately
their implementation differs slightly usually in the header files.
Sometimes people patch the code to work with mingw64 but that breaks
mingw32 (and vice
Thomas, thanks for summarizing that. I see that ZMQ_SOCKS_PROXY isn't
documented yet.
On Wed, Jan 7, 2015 at 4:04 PM, Thomas Rodgers rodg...@twrodgers.com wrote:
GSSAPI is documented -
http://api.zeromq.org/4-1:zmq-gssapi
all of the ZMQ_Xxx items are options are additive and documented -
Thomas Rodgers schreef op de 7e dag van de louwmaand van het jaar 2015:
ZMQ_IDENTITY_FD is get only?
Yes, given a previously set socket identity (see ZMQ_IDENTITY in
http://api.zeromq.org/4-1:zmq-setsockopt), it will return the FD of the
socket associated with that identity.
What is
FD ~= file descriptor.
fd_t, the type this option actually returns, is conditionally defined to be
int or SOCKET depending on platform, same as with ZMQ_FD. It is however,
not the same FD that would be returned by the ZMQ_FD option (I believe it
is the underlying TCP file descriptor or SOCKET in
Peter Kleiweg pklei...@xs4all.nl schreef op 8 januari 2015 03:08:50 CET:
Thomas Rodgers rodg...@twrodgers.com schreef op 8 januari 2015
02:56:18 CET:
FD ~= file descriptor.
fd_t, the type this option actually returns, is conditionally
defined
to be
int or SOCKET depending on
And if fd_t is internal to the C++ code, why is it used in the C API
reference?
As I noted -
Also, fd_t is an internal definition, not exposed in zmq.h so it probably
shouldn't 'leak' into the interface documentation. If these are compelling
enough deficiencies, *perhaps filing a Github
GSSAPI is documented -
http://api.zeromq.org/4-1:zmq-gssapi
all of the ZMQ_Xxx items are options are additive and documented -
http://api.zeromq.org/4-1:zmq-setsockopt
With the exception of ZMQ_SRCFD and ZMQ_SHARED which are message
properties, documented -
Thomas Rodgers schreef op de 7e dag van de louwmaand van het jaar 2015:
GSSAPI is documented -
http://api.zeromq.org/4-1:zmq-gssapi
all of the ZMQ_Xxx items are options are additive and documented -
ZMQ_IDENTITY_FD is get only?
I don't see any documentation for ZMQ_XPUB_NODROP
--
ZMQ_IDENTITY_FD is get only?
Yes, given a previously set socket identity (see ZMQ_IDENTITY in
http://api.zeromq.org/4-1:zmq-setsockopt), it will return the FD of the
socket associated with that identity.
On Wed, Jan 7, 2015 at 11:48 AM, Peter Kleiweg pklei...@xs4all.nl wrote:
Thomas Rodgers
I don't see any documentation for ZMQ_XPUB_NODROP
Issue submitted -
https://github.com/zeromq/libzmq/issues/1287
On Wed, Jan 7, 2015 at 11:48 AM, Peter Kleiweg pklei...@xs4all.nl wrote:
Thomas Rodgers schreef op de 7e dag van de louwmaand van het jaar 2015:
GSSAPI is documented -
For completeness sake, I also added an issue to record the lack of
documentation for ZMQ_SOCKS_PROXY -
https://github.com/zeromq/libzmq/issues/1288
On Wed, Jan 7, 2015 at 9:50 AM, Pieter Hintjens p...@imatix.com wrote:
Thomas, thanks for summarizing that. I see that ZMQ_SOCKS_PROXY isn't
I noticed on the download page there are now versions 4.1.0
(release candidate), 4.0.5, and 3.2.5. None of these releases
were announced on zeromq-announce.
Please post all releases on zeromq-announce.
--
Peter Kleiweg
http://pkleiweg.home.xs4all.nl/
18 matches
Mail list logo
