[zeromq-dev] 0MQ/2.0-beta1 on OSX
steven.mccoy at miru.hk
Mon Jan 18 02:46:24 CET 2010
2010/1/18 Martin Sustrik <sustrik at 250bpm.com>
> This may be tricky. Interface name resolving is done in different ways
> on different OS platforms. On each platform you may get different set of
> errors. Still, we have to ensure that on 0MQ level the sematics of the
> error(s) are consistent across the platforms.
> The quick hack would be to choose a single error code and document is as
> "error when resolving interface name". Any error encountered when
> resolving the name of the interface would then be converted into this
The error code should be ENODEV.
A separate problem is determining whether an interface is operational and
whether it supports bi-directional communication. GetAdaptersInfo() call on
Win32 does not provide any indication of whether an adapter is actually up
and running, I found that GetAdaptersAddresses() does not currently work on
Wine - it always returns success when trying to find the buffer size.
The call GetUniDirectionalAdapterInfo() is rather unusual, the only
unidirectional interfaces I can find are satellite feeds:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the zeromq-dev