Cannot retreive authentication result

[jean-airoldie]

When a connection succeeds the socket is no longer in mute state and can queue outgoing messages via send. The problem is if the authentication failed the user will never know it: he has effectively no way of knowing if his credentials were misconfigured. Here is the issue I filled zeromq/libzmq#3505.

[jean-airoldie]

Really unsure about what the best solution would be.

[jean-airoldie]

My previous solution cannot work if you connect to an external socket. I think I will just create a monitoring socket per thread that will log authentication failures.

[jean-airoldie]

I created this PR that will allow use to use only one thread to log the monitor events from all sockets.

[jean-airoldie]

The PR was merged. I will create another issue for socket event monitoring.

[jean-airoldie]

We can also detect handshake events via the new SocketMonitor API.

[jean-airoldie]

Some kind of wait_handshake helper function would be ideal.

[jean-airoldie]

Conceptually a misconfiguration mechanism is indistinguishable from a missing endpoint. While it might be helpful from the application's perspective to detect misconfigure credentials, I can't really think of a good way to do so.

[jean-airoldie]

This can be fixed by #123