Hi Joel, The monitor event mechanism uses 2 sends to communicate, the first message contains the event details and fd, the second will contain the address, so you need to do a second receive to get the address.
Apparently this was to make it easier for language bindings. Ric. From: "Joel Lauener" <[email protected]> To: "[email protected]" <[email protected]> Date: 05/08/2013 11:02 AM Subject: [zeromq-dev] ROUTER socket and zmq_socket_monitor Sent by: [email protected] Hi, Currently I'm trying to setup a monitor on a ROUTER socket to detect clients disconnections. This system is put in place in addition to an heartbeat mechanism in order to provide faster disconnection detection on the server side. My problem now is that I effectively receive a ZMQ_EVENT_DISCONNECTED event from ZMQ, but the payload of this event only contains "fd" (file descriptor I guess?). In such case is there a way to find the identity of the peer (as set on the client side using the ZMQ_IDENTITY option)? Joel._______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev =========================================================== The information in this email is confidential, and is intended solely for the addressee(s). Access to this email by anyone else is unauthorized and therefore prohibited. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. ===========================================================
<<inline: graycol.gif>>
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
