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)
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
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
12 matches
Mail list logo
