[zeromq-dev] C API changes for ZeroMQ 4.1.0

[Thomas Rodgers]

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 this case).

I am *not* the author of this option, I don't know the intended use case
for it. 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 issue would be in
order?

On Wed, Jan 7, 2015 at 3:37 PM, Peter Kleiweg <pkleiweg at xs4all.nl> wrote:

> 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 an FD? A file descriptor? What is an fd_t?
>
> There is an option ZMQ_FD that returns a file descriptor. That
> is int or SOCKET, for non-windows or windows. Is this similar?
>
>
>
>
> --
> Peter Kleiweg
> http://pkleiweg.home.xs4all.nl/
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20150107/757eae63/attachment.htm>