Simon Giesecke
Simon Giesecke
@fjamal21 Be aware that a socket may be connected to multiple endpoints in general. If there were a function to query this, it would need to return a list of...
This sounds good to me. Maybe transfer the remote address as a string, not in binary form. Then it is easier to also use for transports other than TCP/IP. I...
There are no tests for a websocket `close` command right now. Would that be feasible?
> > > > There are no tests for a websocket `close` command right now. Would that be feasible? > > Yes. The close workflow is implemented, so testing should...
Thank you for considering this. At first sight this sounds as if this would be sufficient for the needs within libzmq. I can totally understand you don't want the scope...
The current implementation is not really good, but the proposed new solution is subject to a race condition: The port may be used by someone else between tmpSocket.close and the...
I don't think there is an error in libzmq. libzmq does not allow calling zmq_close multiple times. This was just clarified in the docs: https://github.com/zeromq/libzmq/pull/2792/files
Option 3 is not possible. zmq_close ultimately deletes the socket object (asynchronously). Accessing a deleted object always leads to undefined behaviour in "native land".
I don't think any of the options 1-3 is a good idea. I suggest the following 4. Remove ZContext.destroySocket (and the list of sockets within a ZContext, which is redundant...
Oh, I found that my main use case is already the default (passing `--disable-cpuid-features-ext` for Pernosco compatibility).